This repository has been archived by the owner. It is now read-only.

npm config https proxy value not used for git+https dependencies #3559

Closed
explunit opened this Issue Jun 14, 2013 · 4 comments

Comments

Projects
None yet
5 participants
@explunit

explunit commented Jun 14, 2013

Steps to reproduce:

  1. do not have https_proxy environment variable set in your host OS
  2. Set the https proxy using the npm config set https-proxy command
  3. npm install jsdoc@3.2.0-dev (or any module that has git+https dependencies)

Expected result: the proxy configuration in npm config is passed to the spawned git process

Actual result: the git process does not use the configured proxy information and an error such as this occurs:

npm ERR! git fetch -a origin (https://github.com/jsdoc3/markdown-js.git) 
error: Failed connect to github.com:443; 
Connection timed out while accessing https://github.com/jsdoc3/markdown-js.git/info/refs?service=git-upload-pack

Workaround: set the https_proxy environment variable in your host OS instead of trying to use the npm config set https-proxy command

@othiym23

This comment has been minimized.

Contributor

othiym23 commented May 4, 2016

It would be extremely helpful to have this set up automatically, I agree. The CLI team will get to this as part of our initiative to improve the CLI's integration with Git, but we may not get to it for a little while, so if somebody else wants to fix it first, we'd be happy to offer time and expertise on how all of this is wired together. Thanks for your time and patience!

burka added a commit to burka/npm that referenced this issue Jan 13, 2017

Update npm.js
Prefill HTTPS_PROXY and HTTP_PROXY from https-proxy and http-proxy if not yet set.
This avoids issues if you are behind a proxy while using 
 - curl (like during webdriver-manager update) 
 - git+https, see npm#3559

burka added a commit to burka/npm that referenced this issue Jan 13, 2017

Use https-proxy config for spawned processes
Prefill HTTPS_PROXY and HTTP_PROXY from https-proxy and http-proxy if not yet set.
This avoids issues if you are behind a proxy while using 
 - curl (like during webdriver-manager update) 
 - git+https, see npm#3559

burka added a commit to burka/npm that referenced this issue Jan 13, 2017

Use https-proxy config for spawned processes
Prefill HTTPS_PROXY and HTTP_PROXY from https-proxy and http-proxy if not yet set.
This avoids issues if you are behind a proxy while using 
 - curl (like during webdriver-manager update) 
 - git+https, see npm#3559

burka added a commit to burka/npm that referenced this issue Jan 16, 2017

Use https-proxy config for spawned processes
Prefill HTTPS_PROXY and HTTP_PROXY from https-proxy and http-proxy if not yet set.
This avoids issues if you are behind a proxy while using
 - curl (like during webdriver-manager update)
 - git+https, see npm#3559
@npm-robot

This comment has been minimized.

npm-robot commented Jun 19, 2017

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Jun 19, 2017

@natejgardner

This comment has been minimized.

natejgardner commented Jul 28, 2017

Any updates on this? This issue makes npm pretty difficult to use behind a corporate proxy.

@muehan

This comment has been minimized.

muehan commented Sep 19, 2017

yes it would be very helpful. proxy makes life hard and missing configuration possabilities doesn't help

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.