Tracking issue: HTTP_PROXY/HTTPS_PROXY/NO_PROXY support in Node.js
- Support https/http proxies via HTTP_PROXY/HTTPS_PROXY/NO_PROXY in fetch() (behind NODE_USE_ENV_PROXY)
- Initial support http: support HTTP[S]_PROXY environment variables in fetch #57165
- align with curl: do not tunnel for http proxy ProxyAgent has different behavior from curl -x undici#4083
- align with curl: support keep-alive Support proxy keep-alive undici#4086
- Support https/http proxies via HTTP_PROXY/HTTPS_PROXY/NO_PROXY in http(s) builtins (behind NODE_USE_ENV_PROXY)
- Initial support for http(s).request and agent: http,https: add built-in proxy support in http/https.request and Agent #58980
- Check that it allows other popular user-land agents (for proxy or not) to operate with/without NODE_USE_ENV_PROXY (investigation)
- Check that it works transparently with popular npm packages that uses http/https.request (investigation)
- Investigate enabling NODE_USE_ENV_PROXY by default
- In fetch() (less risky since fetch is patched less in the wild)
- In http(s) builtins (might be too risky, need to investigate)
- Share code between the fetch and the http(s) builtin implementation (e.g. env var parsing & matching)
- Add a CLI flag that allows enabling proxies: Add
--use-env-proxytoNODE_OPTIONS#59100 - Bug fixes:
--use-env-proxybreaks WebSocket (ws library) long connections via http.request() interception #62054
Some nice to haves (depend on whether there are volunteers that want to pick them up):
- Socks 5 proxy support
- Socks5 proxy support in undici: ProxyAgent: support socks5 protocol undici#2224
- Socks5 proxy support in http/https builtins
- HTTP2 support? Tracking issue: HTTP_PROXY/HTTPS_PROXY/NO_PROXY support in Node.js #57872 (comment)
- Support it properly in the http2.connect
- Until then, make sure fetch() doesn't advertise h2 when proxy is enabled?