HTTP 407 — Proxy Authentication Required
HTTP 407
Proxy Authentication Required
You need to authenticate with a proxy server before your request can go any further.
What 407 actually means
Structurally identical to 401, but the challenge comes from a proxy between you and the site rather than from the site itself. The response carries `Proxy-Authenticate` instead of `WWW-Authenticate`, and you answer with `Proxy-Authorization`. Almost everyone who meets this is on a corporate or school network whose outbound proxy wants credentials.
Common causes
- A corporate or school proxy requiring sign-in for outbound traffic
- Proxy credentials stored in the OS or browser have expired or changed
- An application configured to use a proxy without credentials
- An ISP or captive proxy demanding authentication
If you're just trying to view the page
- Enter your network credentials when the proxy prompts you
- Check your proxy settings in the operating system or browser; a leftover proxy from another network is a common cause
- On a work device, contact IT — the proxy password may have expired with your domain password
- If you are not meant to be behind a proxy at all, turn the proxy setting off
If it's your site
- Command-line tools need the proxy configured explicitly: set `HTTP_PROXY` and `HTTPS_PROXY` with credentials, and `NO_PROXY` for internal hosts
- Build agents and containers behind a corporate proxy need the same environment variables, plus the proxy's CA certificate if it inspects TLS
- Do not confuse this with 401 in error handling — the headers and the party challenging you are different
Reference
- Status code
- 407
- Reason phrase
- Proxy Authentication Required
- Category
- 4xx — Client Error
- Defined in
- RFC 9110 §15.5.8
Common questions
- What does HTTP 407 mean?
- You need to authenticate with a proxy server before your request can go any further. Structurally identical to 401, but the challenge comes from a proxy between you and the site rather than from the site itself. The response carries `Proxy-Authenticate` instead of `WWW-Authenticate`, and you answer with `Proxy-Authorization`.
- How do I fix a 407 error?
- Enter your network credentials when the proxy prompts you
- Is 407 a client error or a server error?
- 407 is in the 4xx range, which means client error. The request itself was the problem, so retrying it unchanged will usually return the same code.
Related pages
- 404 Not Found The server is reachable and working, but there is nothing at the address you ask
- 403 Forbidden The server understood the request and is refusing to allow it, and logging in wi
- 401 Unauthorized You need to authenticate, and either you did not or your credentials were reject
- 429 Too Many Requests You have sent more requests than the service allows in a given period.
- 400 Bad Request The server could not understand the request because something about it is malfor
- 413 Content Too Large The request body is bigger than the server is willing to accept.
- 422 Unprocessable Content The request is well-formed and understood, but the data in it fails the rules.
- 405 Method Not Allowed The URL exists, but it does not accept the HTTP method you used.
- 409 Conflict The request cannot be completed because it clashes with the current state of the
- 415 Unsupported Media Type The server will not accept the format of the body you sent.
- 408 Request Timeout The server gave up waiting for the client to finish sending its request.
- 410 Gone The resource was deliberately removed and is not coming back, and there is no fo