isaacs/npm — Issue #2161: NPM can't parse some http header.
Author: nesukun
Created: 2012-02-15 12:37:03+00:00
State: open

Hello.

I was trying to start a new project using express and used their guide to do so, but found that NPM can't fetch any modules within this network. Judging by the output, it seems that some proxy related http headers fail to be parsed by NPM.

```
C:\Documents and Settings\hernnes\My Documents\Workspace\pruebasnode>npm -g inst
all express
npm http GET http://registry.npmjs.org/express

npm ERR! Error: failed to fetch from registry: express
npm ERR! at c:\program files\nodejs\node_modules\npm\lib\utils\npm-registry-
client\get.js:139:12
npm ERR! at cb (c:\program files\nodejs\node_modules\npm\lib\utils\npm-regis
try-client\request.js:32:9)
npm ERR! at Request._callback (c:\program files\nodejs\node_modules\npm\lib\
utils\npm-registry-client\request.js:137:18)
npm ERR! at Request.callback (c:\program files\nodejs\node_modules\npm\node_
modules\request\main.js:109:22)
npm ERR! at Request. (c:\program files\nodejs\node_modules\npm\no
de_modules\request\main.js:198:58)
npm ERR! at Request.emit (events.js:88:20)
npm ERR! at ClientRequest. (c:\program files\nodejs\node_modules\
npm\node_modules\request\main.js:356:14)
npm ERR! at ClientRequest.emit (events.js:67:17)
npm ERR! at HTTPParser.onIncoming (http.js:1254:11)
npm ERR! at HTTPParser.onHeadersComplete (http.js:102:31)
npm ERR! You may report this log at:
npm ERR!
npm ERR! or email it to:
npm ERR!
npm ERR!
npm ERR! System Windows_NT 5.1.2600
npm ERR! command "c:\\program files\\nodejs\\\\node.exe" "c:\\program files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "express"
npm ERR! cwd C:\Documents and Settings\hernnes\My Documents\Workspace\pruebasnod
e
npm ERR! node -v v0.6.9
npm ERR! npm -v 1.1.0-3
npm ERR! message failed to fetch from registry: express
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Documents and Settings\hernnes\My Documents\Workspace\pruebasnod
e\npm-debug.log
npm not ok
```

I've tried using the http registry instead of https and setting up manually the proxy configuration.