global-tunnel-ng Deletes Proxy Variables After Reading Them
A legacy Node process can still be proxying after http_proxy disappears; inspect the module's retained state and the next client's transport.
In an older application using global-tunnel-ng, initialize can deliberately remove the supported HTTP/HTTPS proxy variables after retaining its selected configuration.
The reason is double handling: another library must not apply the environment proxy again on top of the module's patched HTTP path. A missing process.env.http_proxy therefore does not mean proxying stopped.
Check isProxying for activation and proxyConfig for the retained selection. Avoid logging complete account-bearing configuration or proxyUrl.
If a later client fails after the variables disappear, identify whether it uses the patched HTTP/HTTPS agent, an explicit agent or another transport. A client that independently reads the environment may need its own documented proxy input.
Removing the deletion code from node_modules drops the double-handling guard and can disappear on reinstall. Resolve transport ownership instead. This is a legacy package with documented Node compatibility limits. On a compatible Node version, built-in startup proxy support is one option for standard HTTP clients; custom agents and dispatchers still need their own route.