Is it possible to use the module in https forward mode? I've tried different examples, though without any luck. It works fine for me in reverse proxy mode.
Basically when I try to do:
curl -x localhost:8080 https://github.com
the proxy doesn't respond anything.
Further, is it possible to intercept data in https proxy mode? Like web debugging proxies do, eg. Charles.
I'd be interested in a solution to this: HTTP localhost --> HTTPS remote service.
On a possibly related note, I couldn't get the vows tests in npm test to pass on my Mac (npm 1.2.18 and node 0.10.5)
There is an example right now in the better-examples branch feel free to check it out and close this issue. Also if you got further questions the discuss is here #520
@kalebdf please check out the branch caronte in this repo, master is not compatible with 0.10.x
better-examples is not accessible anymore.
I'm looking to setup an HTTPS forward proxy as well, like the example: curl -x localhost:8080 https://github.com can you please send me an updated link or demo? also, for production, should I use caronte or the regular version?
Any step by step on how to generate the certificate and install it on the client browser (enterprise use case) so that the clients will not get the typical SSL warning?
@damiga looks like examples now live here https://github.com/nodejitsu/node-http-proxy/tree/caronte/examples/http
Have you been able to make it work in SSL man in the middle mode? (forward https to https)?
Nope. I needed this functionality to create a caching proxy for npm registry, but was unable to get it working. Eventually I did everything myself :) You can get a look at repo https://github.com/runk/npm-proxy-cache and particularly https://github.com/runk/npm-proxy-cache/blob/master/lib/proxy.js file. You can get an idea of how it's working there.
hi @runk. Looked at your code but quick question: do I understand correctly that I need an external proxy server running (as identified by mitmSocketPath) ? I hoped this was a self-containing https forward proxy. Any help much appreciated
@gebrits nope, it's just an option to set a path where internal https server keeps its spocket.