HTTP/1.1 Range Requests

E220182
HTTP protocol feature partial content retrieval mechanism

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.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (5)

Label Occurrences
HTTP range requests 1
HTTP range requests specifications 1
HTTP/1.1 Range Requests canonical 1

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.

RFC 7233 → shortName → HTTP/1.1 Range Requests ⓘ
HTTP Working Group → responsibleFor → HTTP/1.1 Range Requests ⓘ
this entity surface form: HTTP range requests specifications
HTTP Working Group → responsibleFor → HTTP/1.1 Range Requests ⓘ
this entity surface form: HTTP/1.1 range requests specification
Content-Range header field → definedIn → HTTP/1.1 Range Requests ⓘ
this entity surface form: Hypertext Transfer Protocol (HTTP/1.1): Range Requests
RFC 2616 → defines → HTTP/1.1 Range Requests ⓘ
this entity surface form: HTTP range requests