Gordon P. Hemsley
Gordon P. Hemsley
In a browsing context, Chrome identifies this as `text/plain` and Firefox identifies this as `audio/flac`.
Yeah, Chrome just displays the `fLaC` text.
You are correct that the **archive MIME type** definition does not include the full **ZIP-based MIME type** definition. It is possible that that was an oversight, but it's also possible...
Indeed, this is an algorithm designed for processing legacy Web content. It should not be updated to include newer HTML elements without significant justification.
@unreleased Modern servers are expected to conform to modern standards and best practices (such as those described in [HTML](https://html.spec.whatwg.org/multipage/) and [Fetch](https://fetch.spec.whatwg.org/)). Failure to do so would be expected to behave...
@padenot Are you sure that Chromium is sniffing this? I'm not seeing it in their sniffing code: https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/net/base/mime_sniffer.cc https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/net/base/mime_sniffer_unittest.cc Though, as you well know, Firefox is: https://hg.mozilla.org/mozilla-central/rev/0bed87941dc5 https://hg.mozilla.org/mozilla-central/file/default/toolkit/components/mediasniffer/nsMediaSniffer.cpp (As I...
> It's however mandatory to implement `HTMLMediaElement` (the Content-Type is to be ignored), so there should be steps to sniff here. I'm not seeing anything in [Media elements](https://html.spec.whatwg.org/multipage/media.html#media-elements) that indicates...
I have confirmed that Chrome identifies this as `text/plain`.
It's possible that 2f83f87025e0392a22c96ea29a60e1e19500c1f8 muddied the waters here, because it lost the distinction between normative and non-normative references. (The reference to [MIMETYPE] was meant to be non-normative.)
I'm not following the logic here. The purpose of nosniff is to treat the Content-Type header as authoritative. If Content-Type is not present, or otherwise has an unuseful value, nosniff...