https://bz.apache.org/bugzilla/show_bug.cgi?id=63932
--- Comment #16 from Michael Osipov <micha...@apache.org> --- (In reply to Mark Thomas from comment #15) > There is a long discussion on the httpd ticket on the merits of adding > "-gzip" or similar to a strong ETag and removing it when seen on a request. > The short version is that unless a server tracks the ETags it edited, the > server can't be sure that the Etag that has "-gzip" on the end has it > because the server added it. > > I'm not sure my "make the strong ETag weak" idea is a good one. I suspect > there might be some edge cases where there would be breakage. Agreed. > Of all the ideas, disabling compression in the presence of a strong ETag > seems like the best solution to me. An open question is do we make this > configurable or do we just do it? If configurable, I'd argue for enabled by > default. I would just do it because anything else would break the RFC for that and this is certainly something we don't want to do. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
