Files
node/lib/internal
Joyee Cheung bedaaa11fc http: support http proxy for fetch under NODE_USE_ENV_PROXY
When enabled, Node.js parses the `HTTP_PROXY`, `HTTPS_PROXY` and
`NO_PROXY` environment variables during startup, and tunnels requests
over the specified proxy.

This currently only affects requests sent over `fetch()`. Support for
other built-in `http` and `https` methods is under way.

PR-URL: https://github.com/nodejs/node/pull/57165
Refs: https://github.com/nodejs/undici/issues/1650
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2025-10-18 12:07:52 +02:00
..
2024-11-27 11:03:39 -05:00
2025-08-04 12:25:31 +02:00
2025-07-28 08:46:16 +02:00
2024-09-12 11:06:49 +02:00
2025-10-11 22:51:07 +02:00
2024-11-27 11:03:39 -05:00
2025-07-24 20:08:23 +02:00
…
…
2025-04-17 10:51:13 -03:00
…
2025-01-05 12:57:35 -05:00
2025-09-20 06:17:06 +00:00
…

Internal Modules

The modules located in lib/internal directory are exclusively meant for internal usage within the Node.js core. They are not intended to be accessed via user modules require(). These modules may change at any point in time. Relying on these internal modules outside the core is not supported and can lead to unpredictable behavior.

In certain scenarios, accessing these internal modules for debugging or experimental purposes might be necessary. Node.js provides the --expose-internals flag to expose these modules to userland code. This flag only exists to assist Node.js maintainers with debugging internals. It is not meant for use outside the project.