3 ms·
I didn't see a lot about websocket routing. I'm in a situation where I want to use secure websockets to lots of backend VMs. In fact, I want each user to get
by darkarmani 14y ago
I didn't see a lot about websocket routing.
I'm in a situation where I want to use secure websockets to lots of backend VMs. In fact, I want each user to get a fresh VM running a websockets server.
Can I reverse-proxy the secure websocket, terminating the SSL, and dynamically forward it along to various backends (VMs)? I would like to multiplex the secure websockets without putting the SSL cert inside each VM.
- themgt 14y agoYeah, node-http-proxy supports this built-in. You terminate the SSL at the proxy and then forward the request to whatever backends you want.
- darkarmani 14y agoAnd you can dynamically add backends based on urls or subdomains? That sounds great if it is true. Do you know how well it scales?
- shykes 14y agoYes, that's what Hipache does. From the project homepage [1]: "Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second." It also addresses your question on scaling: "It currently serves production traffic for tens of thousands of applications hosted on dotCloud. Hipache is based on the node-http-proxy library." [1] http://github.com/dotcloud/hipache http://github.com/dotcloud/hipache