https://bz.apache.org/bugzilla/show_bug.cgi?id=63932
--- Comment #10 from Michael Osipov <micha...@apache.org> --- (In reply to Remy Maucherat from comment #9) > (In reply to Mark Thomas from comment #5) > > Where things get "interesting" is when resources set their own, strong ETag. > > It looks to me that the simplest solution would be for the container > > provided compression to check for the presence of a strong ETag and, if it > > finds one, prepend the weakness indicator to the ETag if it is going to > > compress the resource. > > +1, but this is all academic and I think nobody cares overall. Not really. If you see that how long it took to discuss the HTTPd ticket, I would be inclined to disable compression when the strong validator is turned into a weak one w/o my knowledge. -- 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
