npm install https://atom.io/download/atom-shell/nan-1.6.1.tgz failed

[kunyan]

the url https://atom.io/download/atom-shell/nan-1.6.1.tgz will redirect to a AWS url

when I use npm@1.4.5, it worked, but when I use v2.x. it will show
npm ERR! fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz

I think "npm install" can not handle the case which response http code is 302

[kenany]

@kunyan I cannot reproduce this with the latest stable release of npm (2.13.4).

[kunyan]

@kenany , it's weird, I can reproduce it again and again .
I thought is my network problem , but when I use

curl -O https://atom.io/download/atom-shell/nan-1.6.1.tgz

it can be downloaded. No matter with proxy or not, npm install always failed

[kunyan]

npm ERR! fetch failed https://atom.io/download/atom-shell/nan-1.6.1.tgz npm WARN retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=Parse Error

[kenany]

@kunyan This is with npm@2.13.4?

[kunyan]

@kenany yes.

When I use npm@1.4.25, it will work. no error

[kunyan]

My OS is Fedora 22

[othiym23]

This is (probably) due to a bug in how npm-registry-client (the package that deals with talking to the npm registry and downloading stuff from wherever) handled sending certain HTTP headers (having problems with redirects is a good guess, but npm has handled those fine for years now). There is a branch of npm where work is underway to fix this. The fix will probably land sometime in the next two or three releases. Thanks for the report, and I'm sorry there isn't a really good workaround for this right now!

[falms]

This problem is similar to request/request#1894 and atom/apm#322 .
request@2.67.0 or newer will probably solve this kind of problems.

[npm-robot]

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.