- From: Adam Barth <w3c@adambarth.com>
- Date: Sat, 6 Jun 2009 12:17:19 -0700
- To: "Roy T. Fielding" <fielding@gbiv.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Sat, Jun 6, 2009 at 12:16 AM, Roy T. Fielding <fielding@gbiv.com> wrote: > On Jun 6, 2009, at 8:43 AM, Adam Barth wrote: >> I seem to recall that here are a bunch of servers that send >> Content-Type: application/gzip when they mean Content-Encoding: gzip >> (or is it vice-versa?). I can look up the code if you'd like more >> information. > > No, they send app/gzip as the content-type when they do not want > the recipient to remove the encoding on-the-fly. That is a > typical config for software distribution sites. So, I looked it up. Apparently Apache (maybe an old version?) sends *both* Content-Encoding: gzip and Content-Type: application/gzip for files that end in ".gz". To work around this bug, some popular user agents ignore the Content-Encoding in this case. I'm not suggesting we spec this behavior. The point is more that reality sometimes forces user agents to doctor the Content-Encoding. Adam
Received on Saturday, 6 June 2009 19:18:13 UTC