Re: gzip/mod_deflate - only works with responses, not requests
Helge Hess <[email protected]>
| Newsgroups | gmane.comp.cms.opengroupware.user |
|---|---|
| Message-ID | <[email protected]> |
On 01.08.2008, at 20:51, [email protected] wrote: >> Are you going through any HTTP proxy servers? I've seen those muck- >> up >> when dealing with compressed and uncompressed data. > No. In fact, I've even come across firewalls that will strip out > Accept-Encoding: gzip, so I was checking that header was still being > received by the server. Accept-Encoding is one thing. The server can return compressed content or not. Compressed *request* entities (with content-encoding) is something else, the client would need to resend requests if the server can't decompress (well, there is 100-continue, but that is not widely available). Thats why compressed requests are very rare in HTTP. Besides content-encoding is often a hack anyways (only really works OK with POST and PROPFIND), what we usually want is _transport encoding_ (TE header). Helge -- Helge Hess http://helgehess.eu/ -- OpenGroupware.org Users [email protected] http://mail.opengroupware.org/mailman/listinfo/users