Skip to content
GGleamInsight
Wiki

HTTP 407 Proxy Authentication Required

HTTP 407 Proxy Authentication Required means a client must authenticate with a proxy before it will handle the request. It concerns proxy access, not a login to the destination website.

Published 3 min readUpdated

Definition

HTTP 407 Proxy Authentication Required means a client must authenticate with a proxy before it will handle the request. It concerns proxy access, not a login to the destination website.

How the challenge works

A proxy sits between the client and the requested resource. When proxy authentication is required, the exchange has three distinct parts:

  1. The client sends a request through the proxy.
  2. The proxy responds with status 407 and a Proxy-Authenticate header identifying the authentication scheme and its parameters.
  3. The client may send a new request with a Proxy-Authorization header suitable for that challenge.

Receiving a challenge does not prove that a password is wrong: the original request might not have included proxy credentials at all. Nor does a successful proxy authentication guarantee that the destination will accept the request. Proxy access and access to the target resource are separate decisions. See RFC 9110, proxy authentication fields.

A minimal response example

The following is an illustrative HTTP/1.1 response, not a test against a live proxy or a Gleam endpoint:

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

407 identifies the proxy authentication requirement. Basic names the challenge's authentication scheme; it is an example, not a requirement that every proxy use Basic. The realm identifies a protection space. Configure the client's dedicated proxy authentication settings to answer the actual challenge. Do not place proxy credentials in a destination website's login form or treat a website's Authorization header as a substitute for Proxy-Authorization.

MDN's 407 reference shows the same challenge-and-retry pattern.

407, 401 and 403 describe different conditions

Status Meaning What to inspect first
407 Proxy Authentication Required Authentication is required to use the proxy for this request. Proxy-Authenticate and the client's proxy authentication configuration.
401 Unauthorized The request lacks valid authentication credentials for the target resource. WWW-Authenticate and the target resource's authentication requirements.
403 Forbidden The server understood the request but refuses to fulfill it. The response body and the access policy of the system returning it.

A 403 response is not proof of an IP ban: the standard allows reasons unrelated to credentials. Likewise, a 407 response alone does not show that the destination rejected an exit IP. These distinctions follow RFC 9110, Sections 15.5.2–15.5.8.

What to check when a 407 repeats

For an authorized connection, first verify that the client is using the intended proxy endpoint. Then inspect the challenge and confirm that the client supports the requested authentication scheme and supplies the appropriate proxy credentials. Keep destination authentication settings separate.

If credentials are already configured, check the proxy service's current access requirements and the client's handling of proxy authentication. A status code alone cannot identify the exact configuration error. Repeating an unchanged request or rotating the exit IP does not address the authentication requirement described by 407.

Share only redacted diagnostics when requesting support. Remove credential-bearing headers and secrets from logs. Successful proxy authentication does not grant permission to access or reuse a destination's data; the destination's access rules and applicable usage terms still apply.

References

Sources checked on November 18, 2026.

Frequently asked questions

Does 407 always mean the proxy password is incorrect?

No. It means valid proxy authentication is needed for this request. Credentials may be absent, rejected or unsuitable for the challenge. Inspect the challenge and client configuration before diagnosing a wrong password.

Can logging in to the destination website fix a 407?

A destination login does not satisfy a proxy authentication challenge. Proxy credentials are carried through the proxy authentication mechanism; target-resource authentication uses a separate mechanism.

Is Proxy-Authenticate the same as Proxy-Authorization?

No. Proxy-Authenticate is the proxy's response challenge. Proxy-Authorization is the request field used by the client to supply authentication information to the proxy.

Does changing the exit IP resolve a 407?

The status code asks for proxy authentication, not a different exit address. Correct the authentication configuration first; changing the exit IP is not a protocol-defined remedy for 407.