| Previous | Next |
| HTTP_STATUS_NONE_ACCEPTABLE | HTTP_STATUS_REQUEST_TIMEOUT |
HTTP_STATUS_PROXY_AUTH_REQ
The proxy should identify an acceptable authentication scheme in Proxy-Authenticate. The client responds with Proxy-Authorization on a new or retried request to that proxy.
Check proxy address, credentials, and TLS interception policy. A proxy challenge can occur before a TLS tunnel is created for an HTTPS destination, so sending ordinary origin-server Authorization credentials will not satisfy a 407 challenge.
Operational meaning of HTTP 407 for HTTP_STATUS_PROXY_AUTH_REQ
HTTP 407 (HTTP_STATUS_PROXY_AUTH_REQ) is a client-error response. AllStat records its meaning as “407 Proxy Authentication Required”. For HTTP_STATUS_PROXY_AUTH_REQ, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_PROXY_AUTH_REQ
- Treat HTTP_STATUS_PROXY_AUTH_REQ as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_PROXY_AUTH_REQ, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_PROXY_AUTH_REQ, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 407, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.