代理后面的npm失败，状态为403

Question

我正在尝试在代理后面运行 npm 。我尝试过直接或通过 Authoxy 输入代理：

npm config set proxy http://localhost:8999
npm config set https-proxy http://localhost:8999

无论我使用哪种代理，在运行时我总是会遇到相同的错误npm search：

npm info it worked if it ends with ok
npm verb cli [ 'node', '/usr/local/bin/npm', 'search' ]
npm info using npm@1.1.45
npm info using node@v0.8.4
npm verb config file /Users/xxx/.npmrc
npm verb config file /usr/local/etc/npmrc
npm verb config file /usr/local/lib/node_modules/npm/npmrc
npm WARN Building the local index for the first time, please be patient
npm verb url raw /-/all
npm verb url resolving [ 'https://registry.npmjs.org/', './-/all' ]
npm verb url resolved https://registry.npmjs.org/-/all
npm info retry registry request attempt 1 at 09:48:47
npm http GET https://registry.npmjs.org/-/all
npm info retry will retry, error on last attempt: Error: tunneling socket could not be established, sutatusCode=403
npm info retry registry request attempt 2 at 09:48:57
npm http GET https://registry.npmjs.org/-/all
npm info retry will retry, error on last attempt: Error: tunneling socket could not be established, sutatusCode=403
npm info retry registry request attempt 3 at 09:49:57
npm http GET https://registry.npmjs.org/-/all
npm ERR! Error: tunneling socket could not be established, sutatusCode=403
npm ERR!     at ClientRequest.onConnect (/usr/local/lib/node_modules/npm/node_modules/request/tunnel.js:148:19)
npm ERR!     at ClientRequest.g (events.js:185:14)
npm ERR!     at ClientRequest.EventEmitter.emit (events.js:115:20)
npm ERR!     at Socket.socketOnData (http.js:1383:11)
npm ERR!     at TCP.onread (net.js:410:27)

该命令始终以sutatusCode[sic！] 403 失败-
这表示未经授权。我已将Authoxy设置为不需要用户名/密码。当我绕过Authoxy并以http：// user：pass @
proxy：port的形式提供NTLM代理的真实代理凭据时，会发生相同的错误。

如何通过代理工作？

更新资料

我在NPM项目上创建了一个问题来报告此问题：https :
//github.com/isaacs/npm/issues/2866

Answer 1

是的，所以在发布问题后几分钟之内，我自己在这里找到了答案：https
:
//github.com/npm/npm/issues/2119#issuecomment-5321857

问题似乎是npm在代理上使用HTTPS并不是很好。将注册表URL从HTTPS更改为HTTP可以为我修复此问题：

npm config set registry http://registry.npmjs.org/

我仍然必须提供代理配置（在我的情况下通过Authoxy），但是现在一切正常。

似乎是一个常见问题，但没有充分记录。我希望这里的答案将使人们更容易找到是否遇到此问题。