MIME Sniffing Standard
E48503
The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
All labels observed (1)
| Label | Occurrences |
|---|---|
| MIME Sniffing Standard canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T380427 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIME Sniffing Standard Context triple: [WHATWG, develops, MIME Sniffing Standard]
-
A.
RFC 6176 (prohibition of SSL 2.0)
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally deprecates and forbids the use of the insecure SSL 2.0 protocol in favor of more secure TLS versions.
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MIME Sniffing Standard Target entity description: The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
-
A.
RFC 6176 (prohibition of SSL 2.0)
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally deprecates and forbids the use of the insecure SSL 2.0 protocol in favor of more secure TLS versions.
-
B.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
C.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
WHATWG Living Standard
ⓘ
technical specification ⓘ web standard ⓘ |
| aimsTo |
improve interoperability between web browsers
ⓘ
improve security on the web ⓘ provide consistent MIME sniffing behavior across user agents ⓘ reduce content-type confusion attacks ⓘ reduce cross-site scripting risks caused by incorrect MIME types ⓘ |
| appliesTo |
HTTP clients that implement MIME sniffing
ⓘ
user agents ⓘ web browsers ⓘ |
| defines |
algorithms for determining the media type of resources
ⓘ
rules for MIME type sniffing in web browsers ⓘ sniffing behavior for audio and video ⓘ sniffing behavior for content loaded via other schemes such as data URLs ⓘ sniffing behavior for content served over HTTP ⓘ sniffing behavior for content with incorrect MIME types ⓘ sniffing behavior for content with missing MIME types ⓘ sniffing behavior for images ⓘ sniffing behavior for text and binary resources ⓘ sniffing behavior for unknown or ambiguous content types ⓘ |
| documentationURL | https://mimesniff.spec.whatwg.org/ ⓘ |
| field |
internet protocols
ⓘ
web security ⓘ web technology ⓘ |
| hasGoal |
align browser behavior with security best practices
ⓘ
document de facto browser sniffing behavior ⓘ provide a normative reference for implementers ⓘ |
| influences |
server configuration for Content-Type headers
ⓘ
web application security practices ⓘ |
| maintainer | WHATWG ⓘ |
| publisher | WHATWG ⓘ |
| relatedTo |
Content-Type sniffing security guidelines
ⓘ
Fetch Standard ⓘ HTML Living Standard ⓘ HTTP Content-Type header ⓘ IANA media type registry ⓘ MIME types ⓘ |
| specifies |
byte pattern matching for type detection
ⓘ
conditions under which sniffing may be performed ⓘ conditions under which sniffing must be disabled ⓘ heuristics for distinguishing text from binary data ⓘ interaction with HTTP response headers ⓘ interaction with X-Content-Type-Options header ⓘ sniffing rules for legacy content ⓘ |
| status | living standard ⓘ |
| usedBy |
browser engines
ⓘ
major web browsers ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: MIME Sniffing Standard Description of subject: The MIME Sniffing Standard is a web specification that defines how browsers should determine the media type of resources to improve interoperability and security on the web.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.