On 12/12/2019 15:23, Christopher Schultz wrote: > 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?
Exactly. > 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. Just pinging this thread in case there is someone with a specific use case. At the moment, I'm leaning towards the simplification for Tomcat 10 onwards. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
