HTTP/1.1 Range Requests
E220182
HTTP/1.1 Range Requests is the HTTP mechanism that allows clients to request and receive only specific portions (byte ranges) of a resource, enabling efficient partial downloads and resumable transfers.
All labels observed (5)
| Label | Occurrences |
|---|---|
| HTTP range requests | 1 |
| HTTP range requests specifications | 1 |
| HTTP/1.1 Range Requests canonical | 1 |
| HTTP/1.1 range requests specification | 1 |
| Hypertext Transfer Protocol (HTTP/1.1): Range Requests | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1932791 — 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/1.1 Range Requests Context triple: [RFC 7233, shortName, HTTP/1.1 Range Requests]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
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.
- 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/1.1 Range Requests Target entity description: HTTP/1.1 Range Requests is the HTTP mechanism that allows clients to request and receive only specific portions (byte ranges) of a resource, enabling efficient partial downloads and resumable transfers.
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
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.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP protocol feature
ⓘ
partial content retrieval mechanism ⓘ |
| allowsRandomAccess | true ⓘ |
| clientSendsHeader |
Range: bytes=-500
ⓘ
Range: bytes=0-499 ⓘ Range: bytes=500-999 ⓘ Range: bytes=9500- ⓘ |
| commonlyUsedFor |
audio streaming
ⓘ
large file downloads ⓘ software update downloads ⓘ video streaming ⓘ |
| conditionalWithIfRange | range served only if validator matches ⓘ |
| definedIn |
RFC 7233
ⓘ
RFC 9110 ⓘ |
| enables |
bandwidth optimization
ⓘ
parallel segmented downloads ⓘ partial downloads ⓘ resumable downloads ⓘ seeking within large resources ⓘ |
| fallbackWhenIfRangeFails | 200 OK with full representation ⓘ |
| headerForRangeSupportAdvertisement | Accept-Ranges ⓘ |
| headerForReturnedRange | Content-Range ⓘ |
| improves | user-perceived latency for large resources ⓘ |
| indicatedByServerWith | Accept-Ranges: bytes ⓘ |
| interactsWithCaching | cache may store and serve partial responses ⓘ |
| introducedIn | HTTP/1.1 ⓘ |
| mediaTypeForMultipleRanges | multipart/byteranges ⓘ |
| protocolVersion | HTTP/1.1 ⓘ |
| rangeSpecifierSyntax |
bytes=-suffixLength
ⓘ
bytes=start- ⓘ bytes=start-end ⓘ |
| relatedTo | HTTP byte serving ⓘ |
| requiresServerSupport | true ⓘ |
| responseHeaderForMultipleRanges | multipart/byteranges ⓘ |
| responseHeaderForSingleRange | Content-Range: bytes start-end/total ⓘ |
| serverResponseForSatisfiableRange | 206 Partial Content ⓘ |
| serverResponseForUnsatisfiableRange | 416 Range Not Satisfiable ⓘ |
| supportsMultipleRanges | true ⓘ |
| supportsSingleRange | true ⓘ |
| supportsUnit | bytes ⓘ |
| unsatisfiableRangeCondition | requested range outside current representation length ⓘ |
| unsatisfiableRangeResponseHeader | Content-Range: bytes */totalLength ⓘ |
| usesHeader |
Accept-Ranges
ⓘ
Content-Range ⓘ If-Range ⓘ Range ⓘ |
| usesStatusCode |
206 Partial Content
ⓘ
416 Range Not Satisfiable ⓘ |
| validatorType |
ETag
ⓘ
Last-Modified ⓘ |
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: HTTP/1.1 Range Requests Description of subject: HTTP/1.1 Range Requests is the HTTP mechanism that allows clients to request and receive only specific portions (byte ranges) of a resource, enabling efficient partial downloads and resumable transfers.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: HTTP/1.1 Range Requests
linked to: HTTP/1.1 Range Requests
linked to: HTTP/1.1 Range Requests