{"version":"2.1.283","anchor":"proxy-lookup-no-longer-uses-http-proxy-for-http-urls","canonical_anchor":"proxy-lookup-no-longer-uses-http-proxy-for-http-urls","heading":"One proxy lookup no longer reads HTTP_PROXY","tier":"notice","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/proxy-lookup-no-longer-uses-http-proxy-for-http-urls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### One proxy lookup no longer reads `HTTP_PROXY`\n\nA proxy lookup now checks `HTTPS_PROXY`, then `ALL_PROXY`, then git's system proxy, and ignores `HTTP_PROXY` for every address\n\n**Unclear.** Which Claude Code feature uses this lookup is not settled.\n\n**What**\n\nA proxy is a server that network traffic is routed through, often required on company networks. One of Claude Code's proxy lookups has changed. It used to pick `HTTP_PROXY` or `http_proxy` for addresses that were not `https:`. It now checks the same things in the same order for every address:\n\n- `HTTPS_PROXY` or `https_proxy`\n\n- `ALL_PROXY` or `all_proxy`\n\n- git's system setting, from `git config --system --get http.proxy`\n\n`HTTP_PROXY` and `http_proxy` are no longer read here.\n\n**Why**\n\nIf your proxy is set only in `HTTP_PROXY`, whatever relies on this lookup may no longer go through it. Setting `HTTPS_PROXY` or `ALL_PROXY` as well avoids that.\n\n- Area: Internals\n- Names: `HTTP_PROXY`, `http_proxy`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}