Created
February 8, 2013 16:31
-
-
Save bnoordhuis/4740141 to your computer and use it in GitHub Desktop.
A node.js proxy that accepts HTTP and HTTPS traffic on the same port.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
var fs = require('fs'); | |
var net = require('net'); | |
var http = require('http'); | |
var https = require('https'); | |
var httpAddress = '/path/to/http.sock'; | |
var httpsAddress = '/path/to/https.sock'; | |
fs.unlinkSync(httpAddress); | |
fs.unlinkSync(httpsAddress); | |
var httpsOptions = { | |
key: fs.readFileSync('/path/to/key.pem'), | |
cert: fs.readFileSync('/path/to/cert.pem') | |
}; | |
net.createServer(tcpConnection).listen(8000); | |
http.createServer(httpConnection).listen(httpAddress); | |
https.createServer(httpsOptions, httpsConnection).listen(httpsAddress); | |
function tcpConnection(conn) { | |
conn.once('data', function(buf) { | |
// A TLS handshake record starts with byte 22. | |
var address = (buf[0] === 22) ? httpsAddress : httpAddress; | |
var proxy = net.createConnection(address, function() { | |
proxy.write(buf); | |
conn.pipe(proxy).pipe(conn); | |
}); | |
}); | |
} | |
function httpConnection(req, res) { | |
res.writeHead(200, { 'Content-Length': '4' }); | |
res.end('HTTP'); | |
} | |
function httpsConnection(req, res) { | |
res.writeHead(200, { 'Content-Length': '5' }); | |
res.end('HTTPS'); | |
} |
Does anyone know if any issues exist with this method?
@davidlondono can you provide sample code to reproduce the problem?
Thank you @basarat . but when you use http://IP:PORT
, req.headers['host']
returns IP:PORT
and you should split IP from that and attach :PORT
to that. 😁
This is error generator.
Please add to code:
conn.on("error", err => console.error(err) );
The better code is in the second answer to:
https://stackoverflow.com/questions/22453782/nodejs-http-and-https-over-same-port
But it also returns the same error: write EPIPE (or read ECONNRESET)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It has a problem for multipart requests, the package is too large and some times it my not work