[whatwg] [mimesniff] More issues on the MIME Sniffing spec
poccil14 at gmail.com
Thu Jun 6 02:42:19 PDT 2013
I want to respond to the following issues in the MIME Sniffing spec:
I suggest the following wording for the issue box starting with "A resource is..."
A resource is a data item or message, such as a file or an HTTP response.
I believe this covers the cases that would normally be associated with a MIME type.
I don't think the word "context" needs to be specially defined. The start of section 8
could be rewritten to remove the definition:
In certain cases, it is only useful to identify resources that belong to a certain subset of MIME types. In these cases, it is appropriate to use a context-specific sniffing algorithm in place of the MIME type sniffing algorithm in order to determine the sniffed MIME type of a resource.
This specification defines the following context-specific sniffing algorithms.
As for the Apache bug flag, would it be useful to additionally check the HTTP
headers for a Server header and check if it contains "Apache/"? I don't know which
version of Apache the bug involved was fixed in, so I can't suggest a more accurate
Finally, the Firefox team has recently included a patch to support sniffing MP3
files better  and would like to document it and add it to the MIME Sniffing
spec.  The disadvantage, though, is that more than 512 bytes
are required for an accurate detection.
More information about the whatwg