add http proxy support for ~node@v0.11.x

[zincli]

fixed #7

internal method changed

http.Agent#addRequest(req, host, port, localAddress)  -->  http.Agent#addRequest(req, options)

[mattiash]

I have been running with this patch on both node 0.12.0 and 0.10.33 through an http proxy and it works perfectly. Without this patch, node 0.12.0 failed.

[fenwick67]

@stash Can we get this merged?

[stash-sfdc]

I don't think it actually works with node 0.12 or the new 4.0 implementation. I've been working on a better solution, but I have not had time to finish it yet. Sorry, but can't promise an ETA just yet.

[christian-bromann]

@stash-sfdc it's working great for me too with node v5.1.0, looking forward to your change though. Thanks @zincli anyway. 👍

[stash-sfdc]

@christian-bromann well that's some unexpected good news! what's your use-case of global-tunnel?

[christian-bromann]

@stash-sfdc proxying protractor requests through a transparent proxy

[stash-sfdc]

@christian-bromann thanks for the response, but I think I asked that question the wrong way. Which one of these variations are you using to configure global-tunnel?

[christian-bromann]

the auto-config one:

var globalTunnel = require('global-tunnel');
process.env.http_proxy = process.env.HTTP_PROXY;
globalTunnel.initialize();

Would be nice if global-tunnel wouldn't care about capitalization though

[matttrawicki]

To make Node LTS 4.2.x work, all I needed to do was update tunnel to 0.0.4. My corporate proxy is https over http and I'm using auto-config via env like @christian-bromann . zincli@97910e7 was not needed for my use case, it works with or without those changes. I can submit a PR to bump the dependency version, let me know. Thanks!