RFC 7230
E42395
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.
All labels observed (8)
How this entity was disambiguated
This entity first appeared as the object of triple T311107 — 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 7230 Context triple: [HTTPS, definedIn, RFC 7230]
-
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 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 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.
-
D.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
E.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
- 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 7230 Target entity description: 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.
-
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 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 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.
-
D.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
E.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
- F. None of above. chosen
Statements (53)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ |
| appliesTo |
HTTP/1.1
ⓘ
HTTPS ⓘ |
| category | Standards Track ⓘ |
| defines |
Content-Length header field
ⓘ
HTTP over TLS usage considerations ⓘ
linked to:
HTTPS
HTTP/1.1 connection management ⓘ HTTP/1.1 gateway requirements ⓘ HTTP/1.1 header field formatting rules ⓘ HTTP/1.1 header field syntax ⓘ HTTP/1.1 intermediaries behavior ⓘ HTTP/1.1 message body rules ⓘ HTTP/1.1 message framing ⓘ HTTP/1.1 message syntax ⓘ
linked to:
HTTP/1.1
HTTP/1.1 proxy requirements ⓘ HTTP/1.1 request-line syntax ⓘ HTTP/1.1 routing semantics ⓘ HTTP/1.1 start-line syntax ⓘ HTTP/1.1 status-line syntax ⓘ HTTP/1.1 tunnel behavior ⓘ Host header field requirements ⓘ TE header field ⓘ Trailer header field ⓘ Transfer-Encoding header field ⓘ Upgrade header field ⓘ Via header field ⓘ absolute-form request-target ⓘ asterisk-form request-target ⓘ authority-form request-target ⓘ chunked transfer coding ⓘ connection header field ⓘ connection reuse rules ⓘ header field whitespace handling ⓘ message parsing requirements ⓘ origin-form request-target ⓘ persistent connections ⓘ |
| obsoletes |
RFC 2616
ⓘ
linked to:
RFC 2068
|
| partOf |
HTTP/1.1 specification
ⓘ
linked to:
RFC 7230
|
| partOfSeries |
RFC 7230–RFC 7235 HTTP/1.1 specification set
ⓘ
linked to:
RFC 7230
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedIn |
Request for Comments series
ⓘ
linked to:
RFCs
|
| relatedTo |
RFC 7231
ⓘ
RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| RFCNumber | 7230 ⓘ |
| standardizes |
core HTTP/1.1 message syntax
ⓘ
core HTTP/1.1 routing semantics ⓘ |
| title |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
ⓘ
linked to:
RFC 7230
|
| updates | HTTP/1.1 ⓘ |
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 7230 Description of subject: 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.
Referenced by (14)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 7230
linked to: RFC 7230
linked to: RFC 7230
linked to: RFC 7230