Re: several messages about content sniffing in HTML

James Graham wrote:
> Julian Reschke wrote:
>>> Things aren't specified well enough until I can write an HTTP UA that 
>>> can work in the real world (which, as someone dealing with feeds, I 
>>> can tell you need without question support for content-type sniffing) 
>>> from reading specifications without having to reverse-engineer anything.
>>> ...
>>
>> Doesn't seem to apply to this case.
>>
>> A duplicate Content-Type header response indicates that the response 
>> is invalid.
>>
>> Apparently, most browsers accept the response anyway, some of which 
>> picking the first value, others the second. Both behaviors seem to be 
>> acceptable to users.
>  >
>  > So there's nothing you *need* to reverse engineer in this case.
>  >
> 
> But the fact that you need to examine browsers to determine that the 
> behavior you pick isn't important is itself reverse engineering...

That's true.

What I wanted to point out is that it is *not* necessary for HTML5 to 
pick one specific behavior, and for FF3 to change what it does right now.

BR, Julian