Skip to the content

407 Proxy Authentication Required

A proxy between you and the server wants credentials before it passes the request on. It says how in a Proxy-Authenticate header.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110

What it looks like

HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: Basic realm="Corporate proxy"

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

On networks where traffic to the internet goes through a proxy that requires a login, as in many companies and schools. The proxy answers 407 itself, and the request never reaches the server it was meant for.

What to do about it

Give the client the user name and password for the proxy. Browsers ask for them in a dialog. Command-line tools and libraries have settings for it: curl has --proxy-user, and many programs read the address of the proxy from the environment variables HTTP_PROXY and HTTPS_PROXY. The credentials travel in a Proxy-Authorization header, separate from any login for the site itself.

Not to be confused with

401 UnauthorizedThe server at the end wants credentials, not a proxy on the way.
511 Network Authentication RequiredThe network itself wants you to sign in, usually on a web page.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12