RFC 7235
E41246
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.
All labels observed (7)
How this entity was disambiguated
This entity first appeared as the object of triple T306680 — 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 7235 Context triple: [RFC 9112, obsoletes, RFC 7235]
-
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 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
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 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
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 7235 Target entity description: 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.
-
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 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
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 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
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 (45)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP specification
ⓘ
IETF Request for Comments ⓘ Internet standard ⓘ |
| appliesTo | HTTP/1.1 ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| concernsLayer | application layer ⓘ |
| concernsProtocol |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| defines |
RFC 7235
self-linksurface differs
ⓘ
surface form:
Authentication-Info header field
Authorization header field ⓘ HTTP authentication challenge ⓘ HTTP authentication credentials ⓘ HTTP authentication framework ⓘ Proxy-Authenticate header field ⓘ Proxy-Authentication-Info header field ⓘ Proxy-Authorization header field ⓘ WWW-Authenticate header field ⓘ authentication scheme extensibility rules ⓘ challenge-response authentication mechanism for HTTP ⓘ syntax for Authentication-Info header field ⓘ syntax for Authorization header field ⓘ syntax for Proxy-Authenticate header field ⓘ syntax for Proxy-Authentication-Info header field ⓘ syntax for Proxy-Authorization header field ⓘ syntax for WWW-Authenticate header field ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2617 ⓘ |
| partOf |
HTTP/1.1
ⓘ
surface form:
HTTP/1.1 specification suite
RFC 7235 self-linksurface differs ⓘ
surface form:
RFC 7230–RFC 7235 HTTP/1.1 core specifications
|
| publishedBy | Internet Engineering Task Force ⓘ |
| relatedTo |
Basic authentication
ⓘ
Digest authentication ⓘ |
| specifies |
registry for HTTP authentication schemes
ⓘ
rules for authentication schemes in HTTP ⓘ semantics of HTTP authentication challenges ⓘ semantics of HTTP authentication credentials ⓘ status code 401 Unauthorized semantics ⓘ status code 407 Proxy Authentication Required semantics ⓘ use of authentication parameters in HTTP ⓘ |
| standardizes |
HTTP authentication framework behavior for servers
ⓘ
HTTP authentication framework behavior for user agents ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
RFC 7235
self-linksurface differs
ⓘ
surface form:
Hypertext Transfer Protocol (HTTP/1.1): Authentication
|
| updates | HTTP/1.1 authentication framework ⓘ |
| uses | challenge-response authentication model ⓘ |
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 7235 Description of subject: 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.
Referenced by (15)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Hypertext Transfer Protocol (HTTP/1.1): Authentication
this entity surface form:
Authentication-Info header field
this entity surface form:
RFC 7230–RFC 7235 HTTP/1.1 core specifications
this entity surface form:
HTTP/1.1 authentication specification
this entity surface form:
RFC 7235 Section 2
this entity surface form:
Proxy-Authenticate