On Wed, 12 Jun 2002, Slava Bizyayev wrote:
> Since now the draft tutorial "Features of Content Compression for Different
> Web Clients" (for Part IV: Client side facts and bugs) is available for
> preview and discussion at
> http://devl4.outlook.net/devdoc/Dynagzip/ContentCompressionClients.html .
Here is first part of criticism.
1. You should not mix proxies and browsers.
2. As I said you MS Proxy has not mask at all. "^1\.1 " is not a mask.
"^Squid/" is incorrect mask.
Here is example of Via header of HTTP/1.1 request that goes
though Squid, MS Proxy and Oops:
"1.1 proxy1.domain1.com:3128 (Squid/2.4.STABLE2), 1.0 PROXY2,
proxy3.domain3.com:3128 (Oops 1.5.22f1)"
3. Proxy masks will not help. About 70% of all proxied request are going
through Squid and about 15% are going through MS Proxy.
So much safe way is to disable proxy requests at all instead of tring
to look mask.
Besides I suspect that most proxies handle compressed content incorrectly.
I had checked only Squid, MS Proxy and Oops but there are many another
proxies. So I think you should disable gzip for all proxied request
or enable it for all proxied request if you do not care about old broswer.
mod_deflate by default disable it.
4. You should not unset "Accept-Encoding". Better way is to set
$r->note('disable_gzip').
5. There are two unrelated mod_deflate. First is my mod_deflate for Apache 1.3:
http://sysoev.ru/mod_deflate/
It'd been tested for one year on loaded sites.
Second is expiremental module for Apache2 by Apache tream.
Next part will be about browsers bugs.
Igor Sysoev
http://sysoev.ru
