{"issue":{"state":"closed","created_at":"2011-10-25T21:01:43Z","updated_at":"2011-12-03T17:34:29Z","comments":17,"user":{"gravatar_id":"6c755e06d14248c9c09deddc62d9c686","id":102161,"url":"https://api.github.com/users/eliseosoto","login":"eliseosoto","avatar_url":"https://secure.gravatar.com/avatar/6c755e06d14248c9c09deddc62d9c686?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"I have a problem with npm 1.0.102, reproducible in Mac OS X Lion and Ubuntu 10.04 LTS\r\n\r\nWhen I do anything that requires network interaction like:\r\n\r\n$ npm info express\r\n\r\n    info it worked if it ends with ok\r\n    verbose cli [ 'node', '/usr/bin/npm', 'info', 'express' ]\r\n    info using npm@1.0.102\r\n    info using node@v0.4.11\r\n    verbose config file /Users/BNH378/.npmrc\r\n    verbose config file /usr/etc/npmrc\r\n    verbose config file /usr/lib/node_modules/npm/npmrc\r\n    verbose GET express\r\n    verbose raw, before any munging express\r\n    verbose url resolving [ 'https://registry.npmjs.org/', './express' ]\r\n    verbose url resolved https://registry.npmjs.org/express\r\n    verbose etag \"6H3G82P8IR56OEX7PS15XO3X4\"\r\n    ERR! Error: ENODATA, DNS server returned answer with no data\r\n    ERR!     at IOWatcher.callback (dns.js:74:15)\r\n    ERR! Report this *entire* log at:\r\n    ERR!     <http://github.com/isaacs/npm/issues>\r\n    ERR! or email it to:\r\n    ERR!     <npm-@googlegroups.com>\r\n    ERR! \r\n    ERR! System Darwin 11.2.0\r\n    ERR! command \"node\" \"/usr/bin/npm\" \"info\" \"express\"\r\n    ERR! cwd /Users/BNH378\r\n    ERR! node -v v0.4.11\r\n    ERR! npm -v 1.0.102\r\n    ERR! code ENODATA\r\n    verbose exit [ 1, true ]\r\n\r\n\r\nThere's clearly a problem with how the proxies are used.\r\n\r\nMy proxy env vars are setup correctly:\r\n\r\n    $ export | grep -i proxy\r\n    declare -x http_proxy=\"http://wwwgate0.domain.com:1080\"\r\n    declare -x https_proxy=\"http://wwwgate0.domain.com:1080\"\r\n\r\nAnd this curl works perfectly:\r\n\r\n    curl -k https://registry.npmjs.org/express\r\n\r\nI have tried unsetting https_proxy and setting it to an empty value to no avail.","assignee":null,"id":2049840,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":1595,"labels":[],"title":"Proxy issues npm 1.0.102","html_url":"https://github.com/isaacs/npm/issues/1595","closed_at":"2011-10-26T21:56:42Z","url":"https://api.github.com/repos/isaacs/npm/issues/1595","milestone":null},"action":"created","comment":{"created_at":"2011-12-03T17:34:29Z","updated_at":"2011-12-03T17:34:29Z","user":{"gravatar_id":"a3b2693a9a827a32f59e8c4d8714cd62","id":422013,"url":"https://api.github.com/users/whitman","login":"whitman","avatar_url":"https://secure.gravatar.com/avatar/a3b2693a9a827a32f59e8c4d8714cd62?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"@isaacs I've found http://muffin.doit.org/docs/rfc/tunneling_ssl.html to be useful.  The issue at the moment is that Node doesn't support HTTP/1.0 requests but CONNECT requires it.  I've just submitted a patch for Node at https://github.com/joyent/node/pull/2259","id":3001781,"url":"https://api.github.com/repos/isaacs/npm/issues/comments/3001781"}}