Antwort: Re: Antwort: Re: [Mod_gzip] Gzip encoding, IE 5 & 6, proxy caches, NetCache

[mod_gzip@lists.over.net]

hi Kieran,


> Sorry, I should have added that the proxy was NetCache.
> Try using the proxy I suggested: proxy.ord.marketscore.com 80 .

I would have done so if I could, but as I am sitting behind
some company firewall ... my proxy has to be on _my_ side of
the universe.

> Actually, moreover, the Microsoft article suggests that it is only
> "Name-Space Handler" keys in the registry that are named "http",
> "https", "ftp", "gopher", "file" that cause the problem.

Ah - that's of course different.
But I don't really like to install some unknown foreign soft-
ware to my PC just to reproduce some proxy bug ...

>> But how can a browser "use" a transparent proxy?
>> If the proxy is transparent, then the browser isn't even
>> aware of the proxy's existance.
> There is a fairly specific way in which Netcache proxies serve
> chunked pages, in that they serve the chunks "one chunk per ip
> packet" so it could be something to do with that.
> Maybe I used the term "transparent" incorrectly.
> One can often tell from the HTTP headers that a proxy has been
> used, although it has happened without being explicitly requested.

If it is this proxy's fault, what about blacklisting it?
Does the proxy send a "Via:" header? If so, you could exclude
it by not compressing depending on this HTTP request header
(in mod_gzip: use the "mod_gzip_item_exclude reqheader" direc-
tive). Just ask the proxy provider to play HTTP nicely and not
work without telling everyone about its existance.

Additionally, you should really consider to not compress
chunked content. There is a reason why Kevin Kiley implemen-
ted all this de-chunking stuff ...

Regards, Michael