On 01.06.2010 07:19, Jerome Renard wrote:
In 2010, IMO there is no good reason to have gzip disabled by default.
Almost all websites enable it. There are a handful of prominent
websites that do not. I've had conversations with a few of these
sites. Most of them have not turned it on because they don't
understand what it does, not because they don't have enough CPU. gzip
has been used on the web now for well over 10 years. Only *very* old
browsers, proxies, etc don't have perfect support for gzip.
I remember having a lot of troubles with some combinations of Squid +
IE (6 or so) where the compressed
content was just never gunziped. Was I the only one to get such problems ?
There are still problems with caching proxies, and the behaviour of
mod_deflate has changed several times, even in the 2.2.x lifetime.
There was a lot of discussion about it. As a starter you can read my
last comment in
https://issues.apache.org/bugzilla/show_bug.cgi?id=49358
and then follow the links given there.
In short: mod_deflate uses Content-Encoding instead of Transfer-Encoding
which is supported by the Browsers, but leads to tricky problems when
chosing the right ETag (content equivalence, cache revalidation requests).
Regards,
Rainer
