[whatwg] [mimesniff] Treating application/octet-stream as unknown for sniffing

Boris Zbarsky bzbarsky at MIT.EDU
Wed Nov 28 23:34:52 PST 2012

On 11/29/12 2:32 AM, Boris Zbarsky wrote:
> On 11/29/12 2:07 AM, Gordon P. Hemsley wrote:
>> I imagine this ties in, too, to the issues with sniffing CSS files
>> that has been raised elsewhere:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=560388
>> https://bugzilla.mozilla.org/show_bug.cgi?id=562377
> Neither one of those has anything to do with application/octet-stream as
> far as I can tell.  Those cover cases in which data is sent with either
> no Content-Type header or with such a header which can't even be parsed
> as "major/minor".  Neither of which is true if the data says
> "appliction/octet-stream".

Oh, and the other important bit is that there is no "sniffing" CSS 
involved.  If the load is for a <link rel="stylesheet"> and the server 
doesn't send a content type or sends one that can't be parsed, Gecko 
just treats the data as CSS.  That's not the same thing as sniffing the 
data.  ;)


More information about the whatwg mailing list