Gordon P. Hemsley
Gordon P. Hemsley
For reference, the following two sequences of bytes are detected as WebM in both Firefox and Chrome: **1A 45 DF A3** 81 42 82 84 **77 65 62 6D** **1A...
I don't remember what they do, but I have some tests here: http://whatwg.gphemsley.org/tests/mimesniff/
Likely of relevance (last updated 2015): https://wiki.whatwg.org/wiki/Contexts Which has possibly been replaced by: https://fetch.spec.whatwg.org/#concept-request-destination
From [4.2. MIME type miscellaneous](https://mimesniff.spec.whatwg.org/#mime-type-miscellaneous): > A MIME type is **supported by the user agent** if the user agent has the capability to interpret a resource of that MIME type...
As mentioned above, the original intent of mimesniff was for safely dealing with Web resources missing a Content-Type header or having been tagged with an incorrect MIME type; in other...
> It also might be more accurate to say: > > > If the resource is retrieved directly from the file system, set supplied-type to the MIME type determined by...
[This page](https://brendanzagaeski.appspot.com/0005.html) (quoting from [the PDF spec](https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf)) states: > The second line comment contains 6 high bit characters (displayed as 3 characters in UTF-8 encoding), as required by the "File...
Similar to the concerns I mentioned with WebM in #93, I also wonder if this algorithm is too complex for the purpose it is intending to serve. The mimesniff spec...
Come to think of it, the resulting MIME type is "audio/mpeg". We don't actually have to identify the "Layer III" part at all.
> > Come to think of it, the resulting MIME type is "audio/mpeg". We don't actually have to identify the "Layer III" part at all. > > Well, hmm... >...