Ged Haywood wrote: > > > > I think because many browsers claim to accept gzip encoding and then > > > fail to cope with it. > > > > Such as? > > It's second hand information - Josh had some trouble last year when we > were working on the same project, and I think he eventually gave up > with gzip because of it. He doesn't read the mod_perl list all the > time (being a busy chap:) so I've copied him in on this and maybe > he'll give us the benefit of his experience. Maybe he'll tell you I'm > talking through my hat too... >
There was one odd browser that didn't seem to deal with gzip encoding for type text/html, it was an IE not sure 4.x or 5.x, and when set with a proxy but not really using a proxy, it would render garbage to the screen. This was well over a year ago at this point when this was seen by QA. The compression technique was the same used as Apache::Compress, where all of the data is compressed at once. Apparently, if one tries to compress in chunks instead, that will also result in problems with IE browsers. Note that it wasn't I that gave up on compression for the project, but a lack of management understanding the value of squeezing 40K of HTML down to 5K !! I would compress text/html output to netscape browsers fearlessly, and approach IE browsers more carefully. --Josh _________________________________________________________________ Joshua Chamas Chamas Enterprises Inc. NodeWorks Founder Huntington Beach, CA USA http://www.nodeworks.com 1-714-625-4051
