mirror of
https://github.com/nodejs/node.git
synced 2025-08-15 13:48:44 +02:00
036b1fd66d
This patch implements proxy support for HTTP and HTTPS clients and agents in the `http` and `https` built-ins`. When NODE_USE_ENV_PROXY is set to 1, the default global agent would parse the HTTP_PROXY/http_proxy, HTTPS_PROXY/https_proxy, NO_PROXY/no_proxy settings from the environment variables, and proxy the requests sent through the built-in http/https client accordingly. To support this, `http.Agent` and `https.Agent` now accept a few new options: - `proxyEnv`: when it's an object, the agent would read and parse the HTTP_PROXY/http_proxy, HTTPS_PROXY/https_proxy, NO_PROXY/no_proxy properties from it, and apply them based on the protocol it uses to send requests. This option allows custom agents to reuse built-in proxy support by composing options. Global agents set this to `process.env` when NODE_USE_ENV_PROXY is 1. - `defaultPort` and `protocol`: these allow setting of the default port and protocol of the agents. We also need these when configuring proxy settings and deciding whether a request should be proxied. Implementation-wise, this adds a `ProxyConfig` internal class to handle parsing and application of proxy configurations. The configuration is parsed during agent construction. When requests are made, the `createConnection()` methods on the agents would check whether the request should be proxied. If yes, they either connect to the proxy server (in the case of HTTP reqeusts) or establish a tunnel (in the case of HTTPS requests) through either a TCP socket (if the proxy uses HTTP) or a TLS socket (if the proxy uses HTTPS). When proxying HTTPS requests through a tunnel, the connection listener is invoked after the tunnel is established. Tunnel establishment uses the timeout of the request options, if there is one. Otherwise it uses the timeout of the agent. If an error is encountered during tunnel establishment, an ERR_PROXY_TUNNEL would be emitted on the returned socket. If the proxy server sends a errored status code, the error would contain an `statusCode` property. If the error is caused by timeout, the error would contain a `proxyTunnelTimeout` property. This implementation honors the built-in socket pool and socket limits. Pooled sockets are still keyed by request endpoints, they are just connected to the proxy server instead, and the persistence of the connection can be maintained as long as the proxy server respects connection/proxy-connection or persist by default (HTTP/1.1) PR-URL: https://github.com/nodejs/node/pull/58980 Refs: https://github.com/nodejs/node/issues/57872 Refs: https://github.com/nodejs/node/issues/8381 Refs: https://github.com/nodejs/node/issues/15620 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> |
||
|---|---|---|
| .. | ||
| addons.md | ||
| assert.md | ||
| async_context.md | ||
| async_hooks.md | ||
| buffer.md | ||
| child_process.md | ||
| cli.md | ||
| cluster.md | ||
| console.md | ||
| corepack.md | ||
| crypto.md | ||
| debugger.md | ||
| deprecations.md | ||
| dgram.md | ||
| diagnostics_channel.md | ||
| dns.md | ||
| documentation.md | ||
| domain.md | ||
| embedding.md | ||
| errors.md | ||
| esm.md | ||
| events.md | ||
| fs.md | ||
| globals.md | ||
| http.md | ||
| http2.md | ||
| https.md | ||
| index.md | ||
| inspector.md | ||
| intl.md | ||
| module.md | ||
| modules.md | ||
| n-api.md | ||
| net.md | ||
| os.md | ||
| packages.md | ||
| path.md | ||
| perf_hooks.md | ||
| permissions.md | ||
| process.md | ||
| punycode.md | ||
| querystring.md | ||
| quic.md | ||
| readline.md | ||
| repl.md | ||
| report.md | ||
| single-executable-applications.md | ||
| sqlite.md | ||
| stream.md | ||
| string_decoder.md | ||
| synopsis.md | ||
| test.md | ||
| timers.md | ||
| tls.md | ||
| tracing.md | ||
| tty.md | ||
| typescript.md | ||
| url.md | ||
| util.md | ||
| v8.md | ||
| vm.md | ||
| wasi.md | ||
| webcrypto.md | ||
| webstreams.md | ||
| worker_threads.md | ||
| zlib.md | ||