W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: NEW ISSUE: content sniffing

From: Adam Barth <w3c@adambarth.com>
Date: Wed, 1 Apr 2009 09:20:04 -0700
Message-ID: <7789133a0904010920k412fb98fnafd6c2d72bf05d07@mail.gmail.com>
To: Mark Baker <mark@coactus.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Wed, Apr 1, 2009 at 9:10 AM, Mark Baker <mark@coactus.com> wrote:
> On Wed, Apr 1, 2009 at 12:01 PM, Adam Barth <w3c@adambarth.com> wrote:
>> The current HTTP spec contains a requirement that contradicts this
>> widespread practice.  It seems we should update this part of the spec
>> to reflect reality (and, perhaps, nudge reality into a slightly better
>> equilibrium).
>
> Which requirement is that?

>From http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1

"If and only if the media type is not given by a Content-Type field,
the recipient MAY attempt to guess the media type via inspection of
its content and/or the name extension(s) of the URI used to identify
the resource."

For example, user agents also need to sniff HTTP responses with a
Content-Type of */* in order to be compatible with existing Web
content.

Adam
Received on Wednesday, 1 April 2009 16:20:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:02 GMT