https://bz.apache.org/bugzilla/show_bug.cgi?id=63932
--- Comment #20 from Michael Osipov <[email protected]> --- (In reply to thorsten.meinl from comment #19) > We recently stumbled upon this change because after an upgrade from Tomcat > 8.5 to the lastet Tomcat 9 compression suddenly didn't work any more. We do > use strong ETags because it's the only way to use conditional requests for > PUT and POST operations. > For now we can set noCompressionStrongETag=false and make sure in our > application code that the ETags change with different Accept-Encoding > request headers. What I'm wondering is how this will look in Tomcat 10 when > that property doesn't exist any more and responses with strong ETag are > never compressed. Does this mean we cannot use compression any more at all? > That would be bad since we are sending large JSON payloads which benefit > from compression quite a lot. There is a rant from the Jackson developer that the filesize overweighs the overhead of compression and decompression. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
