You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
At work all of our network traffic to the 'outside' goes through a http proxy (squid) and I'm finding that a lot of modules don't natively support http/https via a proxy. It's generally easy enough to modify the modules to use a http proxy but then I have to patch them at every new release. It would be more difficult to patch modules to use an SSL or SOCKS proxy.
It would be awesome if there was a method of specifying that a nodejs app should use proxy settings either defined in the http_proxy and https_proxy environment variables or on Windows the IE proxy settings. Even more useful would be support for Proxy auto-config files (http://en.wikipedia.org/wiki/Proxy_auto-config) so internal requests can be set to not go via the proxy.
The text was updated successfully, but these errors were encountered:
At work all of our network traffic to the 'outside' goes through a http proxy (squid) and I'm finding that a lot of modules don't natively support http/https via a proxy. It's generally easy enough to modify the modules to use a http proxy but then I have to patch them at every new release. It would be more difficult to patch modules to use an SSL or SOCKS proxy.
It would be awesome if there was a method of specifying that a nodejs app should use proxy settings either defined in the http_proxy and https_proxy environment variables or on Windows the IE proxy settings. Even more useful would be support for Proxy auto-config files (http://en.wikipedia.org/wiki/Proxy_auto-config) so internal requests can be set to not go via the proxy.
The text was updated successfully, but these errors were encountered: