Although I believe that buggy clients are no longer a problem today,
compression may introduce complications when Tomcat runs behind a
reverse proxy as it is often the case. If your front-end server (e.g.
Apache) needs to modify the responses (e.g. with mod_proxy_http), you'll
end up with a quite expensive compress -> decompress -> compress
processing chain on the back end. That is obviously no good idea from a
performance and resource consumption point of view.
So, I'm actually with Rémy. Leave it off by default and point out that
there is an "on" available by explicitly writing compression="off" to
the connector.
Carsten
On Tue, Jun 9, 2020 at 10:20 PM Mark Thomas <ma...@apache.org> wrote:
Hi all,
An enhancement has been opened to enable response compression by default:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64431
In short, the proposal is to change the default for the Connector's
compression attribute from "off" to "on".
This would be for Tomcat 10 onwards only.
The following would be unchanged:
- compressibleMimeType
- compressionMinSize
- noCompressionStrongETag
It would be helpful to know what the range of views of the user
community are on this proposal.
So, thoughts?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
