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

Re: NEW ISSUE: content sniffing

From: Geoffrey Sneddon <foolistbar@googlemail.com>
Date: Wed, 1 Apr 2009 14:42:28 +0100
Message-Id: <DA112AD9-03F1-40AF-A499-1324C16E5ED6@googlemail.com>
To: ietf-http-wg@w3.org

On 31 Mar 2009, at 21:37, David Morris wrote:

> On Tue, 31 Mar 2009, Adam Barth wrote:
>
>> On Tue, Mar 31, 2009 at 12:51 PM, Mark Baker <distobj@acm.org> wrote:
>>> On Tue, Mar 31, 2009 at 3:37 PM, Adam Barth <w3c@adambarth.com>  
>>> wrote:
>>>> When different user agents use different sniffing algorithms,  
>>>> content
>>>> authors pay a large cost, both in terms of compatibility and in  
>>>> terms
>>>> of security.  For user agents that wish to perform sniffing, I  
>>>> think
>>>> we'd be doing the Web a service by specifying which algorithm they
>>>> should use.
>>>
>>> I agree, which is why I suggested a link from 2616bis to the
>>> algorithm.  Do you feel that to be insufficient?  If so, why?
>>
>> I don't have a strong opinion about which document should contain the
>> algorithm, but I think we're better off making the algorithm  
>> normative
>> (for those agents that wish to sniff) rather than informative.  That
>> will help prevent developers of sniffing user agents from  
>> implementing
>> divergent sniffing algorithms.
>
> I disagree ... encoding what is essentially a heuristic algorithm  
> which will need to change as content types morph into standard  
> status is the
> wrong thing to do. Certainly in the HTTP standard.

But the Content-Type sniffing algorithms used in browsers have pretty  
much stagnated. They rarely change, and when they do, it is normally  
to get closer to interoperability. I don't think they change enough  
for it to be an issue. Ideally we probably want the algorithms to get  
frozen where they are now, where they are required for compatibility,  
and never sniff more types.


--
Geoffrey Sneddon
<http://gsnedders.com/>
Received on Wednesday, 1 April 2009 13:43:26 GMT

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