Transfer-Encoding header field
E233793
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Transfer-Encoding header field canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2106021 — 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: Transfer-Encoding header field Context triple: [RFC 7230, defines, Transfer-Encoding header field]
-
A.
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.
-
B.
Accept-Encoding
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.
-
C.
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.
-
D.
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.
-
E.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
- 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: Transfer-Encoding header field Target entity description: 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.
-
A.
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.
-
B.
Accept-Encoding
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.
-
C.
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.
-
D.
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.
-
E.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP header field
ⓘ
message header field ⓘ |
| allows |
sending message bodies of unknown length at start of transfer
ⓘ
streaming of dynamically generated content ⓘ |
| allowsTrailers | true when chunked is used ⓘ |
| appliesTo |
HTTP requests
ⓘ
HTTP responses ⓘ |
| category | message framing mechanism ⓘ |
| controls | transfer codings applied to the message body ⓘ |
| defaultBehavior | no transfer coding is applied if header is absent ⓘ |
| definedIn | HTTP/1.1 ⓘ |
| determines | how the message body is delimited ⓘ |
| differenceFromContentEncoding | applies to transfer over a single connection, not to representation semantics ⓘ |
| distinctFrom | Content-Encoding header field ⓘ |
| governs | order of transfer codings applied ⓘ |
| hasDirective |
chunked
ⓘ
compress ⓘ deflate ⓘ gzip ⓘ trailers ⓘ |
| hasProtocolVersion | HTTP/1.1 ⓘ |
| hasRestriction |
HTTP/1.1 origin servers must not send transfer codings to HTTP/1.0 clients unless compatible
ⓘ
HTTP/1.1 recipients must understand all transfer codings applied ⓘ |
| hasSemantics | each transfer coding is applied to the previous result ⓘ |
| hasTokenType | transfer-coding ⓘ |
| isHopByHop | true ⓘ |
| mayInclude | extension transfer codings ⓘ |
| mustNotBeForwardedBy | HTTP proxies without modification of Connection header ⓘ |
| mutuallyExclusiveWith | Content-Length header field in a single message ⓘ |
| positionInMessage | header section ⓘ |
| primaryMechanism | chunked transfer coding ⓘ |
| processingRequirement |
intermediaries must adjust Content-Length if they decode or re-encode
ⓘ
recipients must remove transfer codings before delivering body to higher layers ⓘ |
| relatedTo | Content-Length header field ⓘ |
| replacedByInHTTP2 | frame-based message delimitation ⓘ |
| replacedByInHTTP3 | frame-based message delimitation ⓘ |
| requiresForChunked |
0-sized final chunk to terminate body
ⓘ
chunk-size line for each chunk ⓘ |
| securityConsideration | improper use can lead to request smuggling vulnerabilities ⓘ |
| specifiedIn |
RFC 7230
ⓘ
RFC 9112 ⓘ |
| statusInHTTP2 | not used in HTTP/2 ⓘ |
| statusInHTTP3 | not used in HTTP/3 ⓘ |
| syntaxExample |
Transfer-Encoding: chunked
ⓘ
Transfer-Encoding: gzip, chunked ⓘ |
| usedFor |
efficient transfer of message bodies
ⓘ
encoding HTTP message bodies ⓘ safe transfer of message bodies ⓘ |
| usedWith |
HTTP
ⓘ
surface form:
HTTP persistent connections
|
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: Transfer-Encoding header field Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.