Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for remote proxy usage #5

Closed
tuxmea opened this issue Jan 15, 2014 · 2 comments
Closed

Add support for remote proxy usage #5

tuxmea opened this issue Jan 15, 2014 · 2 comments

Comments

@tuxmea
Copy link

tuxmea commented Jan 15, 2014

I planned to use npm-lazy-mirror in an internal network where all systems have to use a proxy for outbound connections.
The npm-lazy-mirror does not honor npm proxy settings (npm config) or http_proxy/https_proxy environment variables.

Either use the defaults (from npm or env variables) or allow a configuration section for proxy configuration.

@jdpaton
Copy link
Contributor

jdpaton commented Jan 17, 2014

To elaborate on this the search order for proxy settings is now:

  1. CLI option flags --http_proxy, --https_proxy
  2. Reading from npm config proxy/https-proxy
  3. Environment variables HTTP{S}_PROXY

Tested with mitmproxy.

HTH.

jdpaton added a commit that referenced this issue Jan 17, 2014
@jandubois
Copy link

Why use only HTTP_PROXY but not http_proxy evnironment variables? I find that most apps either only support the lowercase variant (git, curl), or both, but only supporting uppercase seems rare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants