Igor Sysoev wrote: > The main problem is proxies, especially Squid (~70% of all proxies) > Proxies can store compressed response and return it to browser > that does not understand gzipped content.
Is this verified behavior? If a proxy returns compressed content to a
browser that cannot handle it, then the content negotiation function
inside the proxy is broken - and as squid has an active developer
community, I seriously doubt that a bug this serious would go unfixed.
RFC2616 describes the "Vary" header, which helps determine on what basis
a document was negotiated. mod_deflate should use content negotiation
and the presence of the Vary header to determine what to do, as is laid
down in the HTTP spec.
> So you should by default disable encoding for requests
> with "Via" header and HTTP/1.0 requests (HTTP/1.1-compatible
> proxy must set "Via" header, HTTP/1.0-compatible should but not have).
I disagree. Virtually all content is going to go through a proxy of some
kind before reaching a browser. Doing this will effective render
mod_deflate useless.
mod_deflate should behave according to RFC2616 - and you won't have
problems.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
