W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2010

Re: Content Sniffing impact on HTTPbis - #155

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 26 Jan 2010 20:24:19 +0000
Message-ID: <7789133a1001261224n6397b60djf4471d0202d12c5b@mail.gmail.com>
To: Adrien de Croy <adrien@qbik.com>
Cc: Jamie Lokier <jamie@shareable.org>, ietf-http-wg@w3.org
On Sun, Jun 14, 2009 at 1:18 AM, Adrien de Croy <adrien@qbik.com> wrote:
> OK..This does raise the question of what does a server do.
>
> I don't know of any servers (in my relatively limited knowledge of servers)
> that doesn't just use the file extension to choose content type when
> serving.
> If the served type is supposed to be the authoritative reference, you get
> problems when a server has a smaller database of extension-to-type than the
> client.
>
> Otherwise you'd need to re-engineer servers so that content providers can
> manually specify content type when providing content.  That then means
> authors need to know about registered types etc.
>
> So I can't see this changing any time soon, no matter what we write into
> specs.

Servers are free to select the Content-Type header they send in any
way they choose.  The requirements w.r.t. not using the file extension
over HTTP are for user agents.

Adam
Received on Tuesday, 26 January 2010 20:25:12 GMT

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