HTTP Content-Type header

E242831

HTTP header field request header field response header field

The HTTP Content-Type header is a response header that tells clients the media type and character encoding of the returned content so they can interpret it correctly.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (3)

Label	Occurrences
Content-Type	1
Content-Type HTTP header	1
HTTP Content-Type header canonical	1

How this entity was disambiguated

This entity first appeared as the object of triple T2174894 — 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: HTTP Content-Type header
Context triple: [MIME Sniffing Standard, relatedTo, HTTP Content-Type header]

A. HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
B. Transfer-Encoding header field
The Transfer-Encoding header field is an HTTP/1.1 mechanism that specifies how a message body is encoded for safe and efficient transfer between client and server, such as using chunked encoding.
C. Content-Range header field
The Content-Range header field is an HTTP response header used to indicate the specific byte range of a resource being returned, typically in support of partial content delivery and resumable downloads.
D. MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
E. Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
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: HTTP Content-Type header
Target entity description: The HTTP Content-Type header is a response header that tells clients the media type and character encoding of the returned content so they can interpret it correctly.

A. HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
B. Transfer-Encoding header field
The Transfer-Encoding header field is an HTTP/1.1 mechanism that specifies how a message body is encoded for safe and efficient transfer between client and server, such as using chunked encoding.
C. Content-Range header field
The Content-Range header field is an HTTP response header used to indicate the specific byte range of a resource being returned, typically in support of partial content delivery and resumable downloads.
D. MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
E. Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
F. None of above. chosen

Statements (48)

Predicate	Object
instanceOf	HTTP header field ⓘ request header field ⓘ response header field ⓘ
category	representation metadata header ⓘ
definedIn	RFC 7231 ⓘ RFC 9110 ⓘ
determines	how the client processes the response body ⓘ how the client renders or handles content ⓘ
exampleValue	application/json ⓘ image/png ⓘ text/html; charset=UTF-8 ⓘ text/plain; charset=utf-8 ⓘ
governs	parsing of text-based formats ⓘ selection of appropriate application handler ⓘ
hasAbbreviation	Content-Type ⓘ
hasComponent	media type ⓘ optional charset parameter ⓘ
hasDefaultBehavior	may be inferred by user agents when missing ⓘ
hasParameter	boundary ⓘ charset ⓘ media type specific parameters ⓘ
hasPurpose	to indicate the character encoding of the message body ⓘ to indicate the media type of the message body ⓘ
hasSyntax	Content-Type: type/subtype[; parameter=value] ⓘ
headerName	Content-Type ⓘ
interpretedBy	HTTP clients ⓘ HTTP user agents ⓘ web browsers ⓘ
mayBeOverriddenBy	Content-Disposition header in some download scenarios ⓘ
partOf	Hypertext Transfer Protocol ⓘ linked to: HTTP
relatedConcept	content negotiation ⓘ
relatedHeader	Accept header ⓘ Content-Encoding header ⓘ Content-Language header ⓘ Content-Length header ⓘ
relatesTo	MIME ⓘ MIME type ⓘ
securityConsideration	incorrect value can cause content sniffing vulnerabilities ⓘ should match actual media type of content ⓘ
usedFor	indicating CSS stylesheets ⓘ indicating HTML documents ⓘ indicating JSON API responses ⓘ indicating audio formats ⓘ indicating image formats ⓘ indicating video formats ⓘ
usedIn	HTTP request ⓘ HTTP response ⓘ
usesRegistry	IANA media types registry ⓘ linked to: IANA media type registry

How these facts were elicited

Referenced by (3)

Full triples — surface form annotated when it differs from this entity's canonical label.

MIME Sniffing Standard → relatedTo → HTTP Content-Type header ⓘ

RFC 2068 → definesHeaderField → Content-Type ⓘ

linked to: HTTP Content-Type header

IANA media type registry → relatedTo → Content-Type HTTP header ⓘ