RFC 7233
E40982
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 7233 canonical | 10 |
| Hypertext Transfer Protocol (HTTP/1.1): Range Requests | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T306678 — 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: RFC 7233 Context triple: [RFC 9112, obsoletes, RFC 7233]
-
A.
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.
-
B.
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.
-
C.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
D.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- 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: RFC 7233 Target entity description: RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
A.
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.
-
B.
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.
-
C.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
D.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP/1.1 specification
ⓘ
IETF standard ⓘ Request for Comments ⓘ |
| appliesTo | HTTP/1.1 ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
206 Partial Content status code semantics
ⓘ
416 Range Not Satisfiable status code semantics ⓘ Accept-Ranges header field ⓘ Content-Range header field ⓘ HTTP range requests ⓘ If-Range header field ⓘ
linked to:
RFC 7232
Range request header fields ⓘ byte-range requests ⓘ multipart/byteranges media type usage ⓘ multiple range requests in a single HTTP message ⓘ partial content delivery for HTTP resources ⓘ |
| intendedFor |
HTTP client developers
ⓘ
HTTP implementers ⓘ web server developers ⓘ |
| obsoletes |
RFC 2616 (range-related parts)
ⓘ
linked to:
RFC 7232
|
| partOf |
HTTP/1.1 core specification set
ⓘ
linked to:
HTTP/1.1
|
| protocol |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 7230
ⓘ
RFC 7231 ⓘ RFC 7232 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| RFCNumber | 7233 ⓘ |
| shortName | HTTP/1.1 Range Requests ⓘ |
| specifies |
caching behavior for partial content
ⓘ
requirements for intermediaries handling range requests ⓘ requirements for origin servers handling range requests ⓘ requirements for user agents issuing range requests ⓘ rules for combining ranges ⓘ rules for unsatisfiable ranges ⓘ semantics of partial responses ⓘ semantics of range retrieval requests ⓘ validation requirements for range requests ⓘ |
| standardizes |
partial retrieval of representations
ⓘ
use of byte ranges in HTTP ⓘ |
| status | Internet Standard ⓘ |
| title |
Hypertext Transfer Protocol (HTTP/1.1): Range Requests
ⓘ
linked to:
RFC 7233
|
| useCase |
efficient media streaming
ⓘ
resuming interrupted downloads ⓘ retrieving subsets of large resources ⓘ |
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: RFC 7233 Description of subject: RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
Referenced by (11)
Full triples — surface form annotated when it differs from this entity's canonical label.