-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Arief,
On 12/12/19 00:25, Arief Hasani wrote: > IMHO, being able to override form HTTP1.1 conf is all good as user > could easily assume that if not specified in the upgrade than use > http1.1 configs I'm not sure you understand the question. Mark is asking if any users in the community are finding that they need to independently configure specific parts of the HTTP/<2 versus h2 *for the same port*. Thinks like the compression, keepalives, max headers/trailers, timeouts, sendfile config, etc. Does it ever make sense to have sendFile enabled on the HTTP/1.1 connector but disable sendFile if the client upgrades to h2? The suspicion is that identical configuration is acceptable. Mark is trying to ask if there are any exceptions before we simplify the code which handles the configuration. If you have a specific use-case, please explain. - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl3yW1gACgkQHPApP6U8 pFhXZw/+NyYQOJ2NQ6O5sMrfBefPuqz3GKCWW5dXS5scIJJ/3tSym1RENgPA4kp9 Bt0SSTm550MutJso1wl7jKTdYXdfF6NVzCqtsfFPeXSsDj8C9qU0oCeCQItBtjTB 7WpjFSh2Lo6hdkJilwsu7MhxozAkbzcBj6dlQY5xugE5wgy5XpolyvZ9opa3W77T MyjbyISxQxa1K9HQMvRbcPFSTwkDHMTIuXFmOXViMGwEtcMqOGdepBEgtcfHFF8K xIzNbOfgotsAy1aFc7bWwKj+1JgwMqf4YEf8dxCDYjSzAJl5O9UaXVPUhytHqBii uKJCfa18wrU1gMgc0WjbztQctAPvEedncpI81kx2cJhdXa65AY466QDrcOUcsa7O L51d3FkCl0BG6jPNgXWljDeW+MtJyN20KZD83Js5OJKrFuF+D9VR0k97c+tlk4Jd U+KcVCakRLgccVJ9Ah3yzPTvwUAR0OUepYs5XxpXbRxtxrJy+wLfXhGpZysV1lnQ 7oD6PNKxm34EOwwYHkHOVN/BmTU3uX1UJ1lD4mjQijRTr/85PXAoD76nt7lGvNan PUw1XKDNpBGvGD2jok1acooLJjkdUppDiTsd9PRtmkTDaAQxpCVFEgjT305rm6Ve oClnzanF7lRwe69GWBhkjgn2RjdV7eQ5Ogy6XbsaeoVNIpYX1gk= =qIaw -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
