- From: Peter Occil <poccil14@gmail.com>
- Date: Thu, 6 Jun 2013 05:42:19 -0400
- To: "WHATWG" <whatwg@whatwg.org>
- Cc: "Gordon P. Hemsley" <gphemsley@gmail.com>
I want to respond to the following issues in the MIME Sniffing spec: Resources 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. Contexts 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. ]] Apache Bug 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 string check. MP3 Sniffing Finally, the Firefox team has recently included a patch to support sniffing MP3 files better [1] and would like to document it and add it to the MIME Sniffing spec. [2] The disadvantage, though, is that more than 512 bytes are required for an accurate detection. --Peter [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=862088 [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=879429
Received on Thursday, 6 June 2013 09:43:02 UTC