Proxy-Authorization
E748453
Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Proxy-Authorization canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8672374 — 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: Proxy-Authorization Context triple: [RFC 2617, definesHeaderField, Proxy-Authorization]
-
A.
Authentication Header
Authentication Header is an IPsec protocol that provides connectionless integrity and data origin authentication for IP packets, optionally protecting against replay attacks.
-
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 2617
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
D.
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.
-
E.
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.
- 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: Proxy-Authorization Target entity description: Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
-
A.
Authentication Header
Authentication Header is an IPsec protocol that provides connectionless integrity and data origin authentication for IP packets, optionally protecting against replay attacks.
-
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 2617
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP header field
ⓘ
request header ⓘ |
| appliesTo | requests sent via an authenticating proxy ⓘ |
| authenticationLayer | application layer ⓘ |
| belongsTo | IANA Message Headers registry ⓘ |
| bestPractice | use only over HTTPS or other secure transport ⓘ |
| canBeRepeated | no, typically appears at most once per request ⓘ |
| category | HTTP authentication header ⓘ |
| definedIn |
Hypertext Transfer Protocol (HTTP) Authentication framework
ⓘ
linked to:
HTTP authentication framework
RFC 7235 ⓘ |
| direction | client-to-proxy ⓘ |
| distinctFrom | Authorization header ⓘ |
| encodingRule | header field value is textual ⓘ |
| exampleValue |
Proxy-Authorization: Basic <credentials>
ⓘ
Proxy-Authorization: Digest <parameters> ⓘ |
| governedBy | HTTP authentication framework ⓘ |
| hasComponent |
authentication scheme
ⓘ
credentials ⓘ |
| hasScope | proxy authentication ⓘ |
| headerName | Proxy-Authorization ⓘ |
| ignoredBy | origin server in normal operation ⓘ |
| introducedIn | HTTP/1.1 ⓘ |
| mayContain | auth-params ⓘ |
| mustComplyWith | HTTP header field syntax rules ⓘ |
| notUsedFor | origin server authentication ⓘ |
| partOf | HTTP/1.1 protocol ⓘ |
| position | HTTP header section of the request ⓘ |
| processingBy | intermediate proxy server ⓘ |
| relatedTo |
Authorization header
ⓘ
Proxy-Authenticate ⓘ |
| requires | prior Proxy-Authenticate challenge from proxy ⓘ |
| securityConsideration |
Basic authentication sends credentials in an easily decodable form
ⓘ
credentials may be exposed if not used over TLS ⓘ |
| supportsScheme |
Basic
ⓘ
Bearer ⓘ Digest ⓘ Negotiate ⓘ custom authentication schemes ⓘ |
| triggeredBy | 407 Proxy Authentication Required response ⓘ |
| usedBy |
HTTP clients
ⓘ
HTTP libraries ⓘ web browsers ⓘ |
| usedFor |
authenticating a client to a proxy
ⓘ
providing credentials to a proxy server ⓘ |
| usedIn | HTTP request message ⓘ |
| usedWithStatusCode | 407 ⓘ |
| visibility | may be logged by proxies if not configured securely ⓘ |
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: Proxy-Authorization Description of subject: Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.