Definition
NO_PROXY is a client-supported environment setting that excludes specified destinations from proxy use. Matching requests can connect directly even when other proxy environment variables are set.
An exception list, not an access list
HTTPX documents NO_PROXY as a comma-separated list of hostnames or URLs for which the proxy is disabled. This changes the client’s route for matching requests. It does not grant permission to access those hosts or add a source address to a proxy account’s allowlist.
An illustrative local-service exception can prevent traffic intended for a development service from being sent to an external proxy. The appropriate entries depend on the environment and the client’s matching behavior.
Why a mixed route is easy to miss
One application can use a proxy for one destination and a direct connection for another. An exit-address test to a non-excluded host therefore does not prove the path used for an excluded host. Inspect the relevant destination, not just whether any proxy variable exists.
Clients differ in accepted syntax and matching rules. Do not assume that hostname suffixes, ports, IP ranges, or wildcard conventions work identically in every library. Use the documentation for the client version running the workload.
Review exclusions with the task
Keep exclusions specific and understandable. If a request unexpectedly bypasses the proxy, check inherited environment variables and application-level proxy controls before changing gateway or credential settings.
Where the environment requires a proxy for all external access, an unintended exclusion can break the expected route. Correct the configuration in accordance with network policy rather than using exceptions to avoid required controls. Re-run the authorized connection check from the actual application process.
Sources
Sources checked on November 18, 2026. Examples are illustrative, not measurements of a live proxy service.
Related concepts
Frequently asked questions
Is NO_PROXY an IP allowlist for a provider?
No. It is a client routing exclusion. A provider allowlist controls which sources may use the proxy.
Does NO_PROXY disable the proxy for every request?
Only matching destinations under the client’s rules are excluded; other requests can still use the proxy.
Can a successful proxy test miss an exclusion problem?
Yes. A test to a different hostname may use a different route.