Apache::Compress - any caveats?

[Mark Maunder <ma...@swiftcamel.com>]

I'm using Apache::Compress with Apache::Filter successfully and have
modified it to only compress text/html (due to a bug in netscape 4.7).
It's working fine with all version of the following browsers: Konqueror,
Netscape, IE, Opera, Lynx and AOL. I was wondering if anyone has had any
bad experiences with it or knows of any caveats? I noticed that there
are very few sites out there using Content-Encoding: gzip - in fact
yahoo was the only one I could find. Is there a reason for this (besides
a bit of extra CPU usage on the server side)?

Re: Apache::Compress - any caveats?

[Mark Maunder <ma...@swiftcamel.com>]

Ged Haywood wrote:

> Hi there,
>
> On Wed, 24 Oct 2001, Mark Maunder wrote:
>
> > I noticed that there are very few sites out there using
> > Content-Encoding: gzip - in fact yahoo was the only one I could
> > find. Is there a reason for this
>
> I think because many browsers claim to accept gzip encoding and then
> fail to cope with it.

The only bug I have noticed is Netscape 4.7 which does not like anything
other than HTML to be compressed. So the only thing I'm compressing is
text/html. I dont know of any browsers that wont accept compressed html
(so far).

Re: Apache::Compress - any caveats?

[Ged Haywood <ge...@www2.jubileegroup.co.uk>]

Hi there,

On Wed, 24 Oct 2001, Mark Maunder wrote:

> I noticed that there are very few sites out there using
> Content-Encoding: gzip - in fact yahoo was the only one I could
> find. Is there a reason for this

I think because many browsers claim to accept gzip encoding and then
fail to cope with it.

73,
Ged.