Am Montag, 26. August 2013, 10:15:19 schrieb Daniel Lescohier: > This article recommends not doing BrowserMatches for http > compression any more. E.g., IE was fixed in XP Service Pack 2 in > year 2004. > > http://zoompf.com/blog/2012/02/lose-the-wait-http-compression > > It is also interesting to read about the problem with the 'deflate' > codec, with the result being to always use 'gzip' codec, not > 'deflate' codec.
I have seen deflate related problems with fully patched IE6 much later than 2004, more like 2009 or so. But I would still think that the time to add work-arounds for IE6 or even older browsers is long past. I am +1 to removing them all from 2.4. > On Fri, Aug 23, 2013 at 4:31 PM, Eric Covener <cove...@gmail.com> wrote: > > Is there any sense in maintaining the netscape 4 workarounds in > > the > > sample deflate config in 2.4 and later? > > > > They end up setting a Vary on User-Agent which is terrible on > > caches. I recently assisted a user who skipped the Vary and they > > ended up corrupting caches instead. > > > > http://httpd.apache.org/docs/2.4/mod/mod_deflate.html > > > > # Netscape 4.x has some problems... > > BrowserMatch ^Mozilla/4 gzip-only-text/html > > > > # Netscape 4.06-4.08 have some more problems > > BrowserMatch ^Mozilla/4\.0[678] no-gzip > > > > # MSIE masquerades as Netscape, but it is fine > > BrowserMatch \bMSIE !no-gzip !gzip-only-text/html > > # Don't compress images > > SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip > > dont-vary > > > > # Make sure proxies don't deliver the wrong content > > Header append Vary User-Agent env=!dont-vary > > > > In 2.2, I would add a warning about caches, but leave the canned > > example. > > > > -- > > Eric Covener > > cove...@gmail.com
