RFC 2617
E205827
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
All labels observed (4)
| Label | Occurrences |
|---|---|
| RFC 2617 canonical | 3 |
| HTTP Authentication: Basic and Digest Access Authentication | 1 |
| HTTP Digest Access Authentication | 1 |
| HTTP Digest Access Authentication as refined in RFC 7616 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1844270 — 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 2617 Context triple: [RFC 7235, obsoletes, RFC 2617]
-
A.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
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.
-
D.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
E.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
- 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 2617 Target entity description: RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
A.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
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.
-
D.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
E.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
- F. None of above. chosen
Statements (29)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| authenticationScheme |
Basic
ⓘ
Digest ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP Basic authentication
ⓘ
HTTP Digest Access Authentication ⓘ
linked to:
HTTP authentication framework
|
| definesHeaderField |
Authorization
ⓘ
Proxy-Authenticate ⓘ
linked to:
RFC 7235
Proxy-Authorization ⓘ WWW-Authenticate ⓘ
linked to:
HTTP authentication framework
|
| definesMechanismFor | HTTP authentication ⓘ |
| obsoletedBy | RFC 7235 ⓘ |
| obsoletes | RFC 2069 ⓘ |
| protocol |
HTTP
ⓘ
Hypertext Transfer Protocol ⓘ
linked to:
HTTP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relationship | Part of the HTTP/1.1 specification family ⓘ |
| securityProperty |
Basic transmits credentials in an easily decodable form
ⓘ
Digest provides protection against replay attacks using nonces ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Obsoleted ⓘ |
| supersededBy | HTTP Authentication framework defined in RFC 7235 ⓘ |
| title |
HTTP Authentication: Basic and Digest Access Authentication
ⓘ
linked to:
RFC 2617
|
| updatesSpecificationOf | HTTP/1.1 authentication ⓘ |
| useCase |
User authentication to HTTP origin servers
ⓘ
User authentication to HTTP proxies ⓘ |
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 2617 Description of subject: RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 2617
linked to: RFC 2617
linked to: RFC 2617