slightly off-topic (although I am trying to shoe-horn this stuff into a ZF
context):
So, this looks to be basics of the de-facto (apache.org) recommended
mod_deflate .htaccess setup:
AddOutputFilterByType DEFLATE text/html
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
Header append Vary User-Agent
But, my question is, do we even need the BrowserMatch stuff here, and the
adding of 'User-Agent' to the 'Vary' header (which in itself must cause huge
potential-for-caching inefficiency for proxies/network-level-caches)??
Seems all they're doing is saying "don't gzip for old Mozilla 4.0 browsers,
unless they're actually IE". But are any of these non-IE old Mozilla 4.0
browsers still in widespread use, even in the slightest? Is Opera fully gzip
friendly?
Also, what's the deal with the rumoured don't-like-gzip errors with certain
versions of IE 6.0 that occur intermittently? These rules don't seem to care
what IE version it is, so are there any real issues? And what about IE <=
5.5? Not that anyone even makes their sites work in such antiques these
days!
What I'm asking, in a nutshell, is why can't I just do this:
AddOutputFilterByType DEFLATE text/html
..and let mod_deflate automatically take care of choosing whether to gzip
based solely on the 'Accept-Encoding' header, and automatically adding
'Vary: Accept-Encoding' if it gzips?
Jonny
--
View this message in context: http://zend-framework-community.634137.n4.nabble.com/Use-ob-gzhandler-with-ZF-tp668519p3070122.html
Sent from the Zend MVC mailing list archive at Nabble.com.
没有评论:
发表评论