We should give it a try - if it works with most browsers, then we can switch...
At 13:24 25/11/2001, Stanislav Malyshev wrote:
>gzip encoding module now uses Content-Encoding header to sign that the
>page uses gzip encoding. Mozilla doesn't handle this 100% good (it saves
>it as zipped, which is
gzip encoding module now uses Content-Encoding header to sign that the
page uses gzip encoding. Mozilla doesn't handle this 100% good (it saves
it as zipped, which is not exactly expected behaviour) and they claim
Transfer-Encoding is the right header to use for in-transfer encoding.
See: http
