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

Re: Content Sniffing impact on HTTPbis - #155

From: Adam Barth <w3c@adambarth.com>
Date: Sat, 13 Jun 2009 18:03:06 -0700
Message-ID: <7789133a0906131803n499d2a5dte630c8b3d43d804b@mail.gmail.com>
To: Adrien de Croy <adrien@qbik.com>
Cc: Jamie Lokier <jamie@shareable.org>, ietf-http-wg@w3.org
On Sat, Jun 13, 2009 at 6:01 PM, Adrien de Croy<adrien@qbik.com> wrote:
> that code shows Chrome using the file extension to look up a content type
> from the windows registry, so it's clearly showing Chrome using the file
> extension to determine content type.  The fact that the DB of extension to
> type is provided by the OS, doesn't alter the fact that Chrome is using it.

You'd have to examine the callers of that function to see what it's
used for.  It might not actually be called at all.  I think it's used
in some security checks for downloaded files.  It's certainly not used
by the sniffing algorithm.

Adam
Received on Sunday, 14 June 2009 01:03:57 GMT

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