The HTTP Proxy-Authenticate response header defines the authentication method that should be used to gain access to a resource behind a proxy server. It authenticates the request to the proxy server, allowing it to transmit the request further.
The Proxy-Authenticate header is sent along with a 407 Proxy Authentication Required.
| Header type | Response header |
|---|---|
| Forbidden header name | no |
Syntax
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
Proxy-Authenticate: Basic Proxy-Authenticate: Basic realm="Access to the internal site"
Specifications
| Specification | Title |
|---|---|
| RFC 7235, section 4.3: Proxy-Authenticate | HTTP/1.1: Authentication |
| RFC 7617 | The 'Basic' HTTP Authentication Scheme |
Browser compatibility
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Update compatibility data on GitHub
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Proxy-Authenticate | Chrome Full support 1 | Edge Full support ≤79 | Firefox Full support 1 | IE ? | Opera Full support Yes | Safari ? | WebView Android Full support 37 | Chrome Android Full support Yes | Firefox Android Full support Yes | Opera Android Full support Yes | Safari iOS ? | Samsung Internet Android Full support Yes |
Legend
- Full support
- Full support
- Compatibility unknown
- Compatibility unknown