Back to blog
Automation6 min read

Proxy Environment Variables Guide

HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY explained — precedence, pitfalls, and tooling compatibility.

HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY explained — precedence, pitfalls, and tooling compatibility.

Core variables

  • HTTP_PROXY / http_proxy
  • HTTPS_PROXY / https_proxy
  • ALL_PROXY for any scheme
  • NO_PROXY for bypass list

Precedence

Lowercase vs uppercase varies by tool. Explicit client config beats env when both are set.

NO_PROXY

Bypass internal APIs and metadata endpoints. Misconfigured NO_PROXY leaks internal calls through paid proxy egress.

Related: curl configuration.

Need proxies at scale?

proxies.st offers health-checked HTTP and SOCKS pools with dashboard access, API keys, and plain-text bulk feeds for pipelines.

Related guides