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

Already on GitHub? Sign in to your account

npm@0.3.17 does not work behind a corporate HTTP proxy. Worked with npm@0.3.15 #753

Closed
anair opened this Issue Mar 26, 2011 · 3 comments

Comments

Projects
None yet
2 participants

anair commented Mar 26, 2011

Works fine after downgrading to 0.3.15

Error message:

$ npm install connect

npm info it worked if it ends with ok
npm info using npm@0.3.17
npm info using node@v0.5.0-pre
npm ERR! Error: ENOTFOUND, Domain name not found
npm ERR! at IOWatcher.callback (dns.js:53:15)
npm ERR! Report this entire log at http://github.com/isaacs/npm/issues
npm ERR! or email it to npm-@googlegroups.com
npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm ERR! System Linux 2.6.18-194.el5
npm ERR! argv { remain: [ 'connect' ],
npm ERR! argv cooked: [ 'install', 'connect' ],
npm ERR! argv original: [ 'install', 'connect' ] }
npm not ok

Owner

isaacs commented Mar 28, 2011

Thank you for this clue! I think I found the issue, releasing a fix in the next few minutes.

Owner

isaacs commented Mar 28, 2011

Closed by 7e4b7bc Set the host header properly with port

@isaacs isaacs closed this Mar 28, 2011

Owner

isaacs commented Mar 28, 2011

Fixed on 0.3.18 and 1.0.1rc0

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