Proxy-Authenticate
Baseline Widely available
This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015.
The HTTP Proxy-Authenticate response header defines the authentication method (or challenge) that should be used to gain access to a resource behind a proxy server.
It is sent in a 407 Proxy Authentication Required response so a client can identify itself to a proxy that requires authentication.
| Header type | Response header |
|---|---|
| Forbidden header name | Yes |
Syntax
http
Proxy-Authenticate: <type> realm=<realm>
Directives
<type>-
Authentication type. A common type is "Basic". IANA maintains a list of authentication schemes.
realm=<realm>-
A description of the protected area, the realm. If no realm is specified, clients often display a formatted host name instead.
Examples
http
Proxy-Authenticate: Basic
Proxy-Authenticate: Basic realm="Access to the internal site"
Specifications
| Specification |
|---|
| HTTP Semantics # field.proxy-authenticate |
Browser compatibility
BCD tables only load in the browser