Accept-Encoding
E200845
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Accept-Encoding canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1812632 — 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: Accept-Encoding Context triple: [RFC 7231, definesHeaderField, Accept-Encoding]
-
A.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
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 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- 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: Accept-Encoding Target entity description: Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
A.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
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 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
E.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf | HTTP request header field ⓘ |
| allows | content negotiation for content-encoding ⓘ |
| canBeOverriddenBy | intermediary proxies ⓘ |
| canInclude |
*
ⓘ
br ⓘ compress ⓘ deflate ⓘ gzip ⓘ identity ⓘ |
| contrastsWith |
Accept header, which negotiates media types
ⓘ
Accept-Charset header, which negotiates character sets ⓘ Accept-Language header, which negotiates natural languages ⓘ |
| defaultSemantics | if header is absent, server may assume client accepts identity encoding only ⓘ |
| definedIn |
RFC 2616
ⓘ
RFC 7231 ⓘ |
| exampleUse | clients advertise support for gzip to receive compressed responses ⓘ |
| fieldType | request header ⓘ |
| fieldValueType | list of codings with optional quality values ⓘ |
| hasPurpose | indicate acceptable content-encoding algorithms to the server ⓘ |
| headerCategory | representation metadata ⓘ |
| headerName | Accept-Encoding ⓘ |
| improves |
bandwidth efficiency
ⓘ
page load performance ⓘ |
| influences | server choice of response content-encoding ⓘ |
| introducedIn | HTTP/1.1 ⓘ |
| isCaseInsensitive | true ⓘ |
| mustNotContain | message body ⓘ |
| partOf | HTTP/1.1 specification ⓘ |
| processingRule |
if no acceptable encoding is available, server may respond with 406 Not Acceptable
ⓘ
server selects one encoding from the acceptable set or returns unencoded content ⓘ |
| relatedSecurityConsideration | compression side-channel attacks such as BREACH ⓘ |
| relatesTo |
Content-Encoding
ⓘ
Transfer-Encoding ⓘ |
| semantics |
higher q value indicates higher preference for an encoding
ⓘ
identity encoding is always acceptable unless explicitly refused with q=0 ⓘ q=0 means encoding is not acceptable ⓘ |
| status | standard header ⓘ |
| supportsParameter |
q (quality value)
ⓘ
wildcard * encoding ⓘ |
| syntaxExample |
Accept-Encoding: gzip, deflate
ⓘ
Accept-Encoding: gzip;q=1.0, br;q=0.8, *;q=0.1 ⓘ |
| usedBy |
HTTP clients
ⓘ
HTTP libraries ⓘ web browsers ⓘ |
| usedFor | HTTP response compression ⓘ |
| usedIn | HTTP requests ⓘ |
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: Accept-Encoding Description of subject: Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.