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

Re: Content Sniffing impact on HTTPbis - #155

From: Adrien de Croy <adrien@qbik.com>
Date: Sun, 14 Jun 2009 13:01:19 +1200
Message-ID: <4A344BDF.4000802@qbik.com>
To: Adam Barth <w3c@adambarth.com>
CC: Jamie Lokier <jamie@shareable.org>, ietf-http-wg@w3.org

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.

Adrien


Adam Barth wrote:
> On Sat, Jun 13, 2009 at 2:57 PM, Adrien de Croy<adrien@qbik.com> wrote:
>   
>> Do you have any information about such APIs in windows?  I'd be keen to look
>> into them further.  I thought I knew win32 API pretty well, and I'm unaware
>> of any function to return the content-type for a file.
>>     
>
> Looks like they're just setting in the registry:
>
> http://src.chromium.org/viewvc/chrome/trunk/src/net/base/platform_mime_util_win.cc
>
> Adam
>   

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
Received on Sunday, 14 June 2009 00:58:33 GMT

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