I am building a HTTP proxy which also listens to HTTPS. HTTPS is just
tunneled through.
If this a HTTPS request, I connect to the origin server using
net.connect({host: 'www.google.com': port: 443}, ...).
I have something set like:
proxy.on(data) { server.write(data) }
server.on(data) {
Got it. My fault.
I was sending the request text (CONNECT www.google.com:443 1.1) to the
server as well.
On Sunday, 3 March 2013 19:25:58 UTC-8, V'Raj Kanwade wrote:
I am building a HTTP proxy which also listens to HTTPS. HTTPS is just
tunneled through.
If this a HTTPS request, I connect
But then, integrating the custom protocol might not be possible right? The
custom protocol is used for admin purposes. This is currently a python
codebase. We are porting it to nodejs. So the client wants to keep the
architecture same.
On Wednesday, 6 February 2013 19:04:11 UTC-8,
I am building a proxy server which needs to listen for both http and https
proxy on same port.
http.createServer does not call response handler for https traffic.
So I created the server using net.createServer. The question I have is, how
can I leverage the http functionality once I have the
the proxy has to listen to http, https
and custom protocol on same port.
On Wednesday, 6 February 2013 10:58:07 UTC-8, V'Raj Kanwade wrote:
I am building a proxy server which needs to listen for both http and https
proxy on same port.
http.createServer does not call response handler for https
I think you forgot link/ info.
On Wednesday, 6 February 2013 18:40:27 UTC-8, Arunoda Susiripala wrote:
I think he is looking for this.
On Thursday, February 7, 2013, Isaac Schlueter wrote:
Why would you want to do this?
Why wouldn't you want http on :80 and https on :443, so that you
