Content-Range header field
E216279
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Content-Range header field canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1932768 — 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: Content-Range header field Context triple: [RFC 7233, defines, Content-Range header field]
-
A.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
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.
RFC 7231
RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
- 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: Content-Range header field Target entity description: 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.
-
A.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
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.
RFC 7231
RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP header field
ⓘ
response header field ⓘ |
| category | HTTP/1.1 range request mechanism ⓘ |
| definedIn |
HTTP/1.1 Range Requests
ⓘ
surface form:
Hypertext Transfer Protocol (HTTP/1.1): Range Requests
RFC 7233 ⓘ |
| direction | response-only header ⓘ |
| errorUsage | used in 416 responses to describe the current length of the selected representation ⓘ |
| exampleUseCase |
resuming an interrupted file download
ⓘ
seeking within a video stream over HTTP ⓘ |
| hasABNF |
Content-Range = byte-content-range / other-content-range
ⓘ
byte-content-range = bytes SP byte-range-resp-spec "/" ( complete-length / "*" ) ⓘ byte-range-resp-spec = ( first-byte-pos "-" last-byte-pos ) / unsatisfied-range ⓘ complete-length = 1*DIGIT ⓘ unsatisfied-range = "*" "/" complete-length ⓘ |
| hasComponent |
complete-length
ⓘ
range-end ⓘ range-start ⓘ unit ⓘ |
| hasSyntaxExample |
Content-Range: bytes 0-499/1234
ⓘ
Content-Range: bytes 500-999/* ⓘ Content-Range: bytes 500-999/1234 ⓘ |
| mustNotAppearWithStatusCode | 200 OK ⓘ |
| notUsedFor | multiple range responses in a single message-body ⓘ |
| primaryUnit | bytes ⓘ |
| rangeUnitExtensibility | allows other range units via other-content-range ⓘ |
| relatedTo |
Accept-Ranges header field
ⓘ
Content-Length header field ⓘ Content-Type header field ⓘ |
| securityConsideration | can reveal resource size information to clients ⓘ |
| semantics |
describes where in the full selected representation the partial payload body is located
ⓘ
indicates the total size of the selected representation when known ⓘ |
| supports | single range responses ⓘ |
| usedFor |
indicating the specific byte range of a selected representation
ⓘ
supporting media streaming ⓘ supporting partial content delivery ⓘ supporting random access to large resources ⓘ supporting resumable downloads ⓘ |
| usedInProtocol | HTTP ⓘ |
| usedWithHeader | Range header field ⓘ |
| usedWithStatusCode |
206 Partial Content
ⓘ
416 Range Not Satisfiable ⓘ |
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: Content-Range header field Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.