4 ms·
Not only that, but letting all traffic through Varnish is not a good utilization of its resources at all. The question is, how could I set up multiple servers
by pestaa 14y ago
Not only that, but letting all traffic through Varnish is not a good utilization of its resources at all.
The question is, how could I set up multiple servers on the same port? Or what else do I need to put in front of Varnish to route WebSocket connections elsewhere?
I'm starting to think this use case is not easy to solve under one IP address.
- 2mur 14y agoNode Http Proxy: https://github.com/nodejitsu/node-http-proxy https://github.com/nodejitsu/node-http-proxy No need for Varnish for proxying your websockets.
- thruflo 14y agoThanks for the link. This looks like an ideal tool to fulfil the same role as Varnish (in the stack I'd outlined) without losing SSL support or allocating one thread per active connection.
- sureshv 14y agoVarnish sits in front on port 80 then proxies based on the VCL configuration, you can parse the HTTP headers/path to pass through appropriately. https://www.varnish-cache.org/docs/trunk/tutorial/websockets.html https://www.varnish-cache.org/docs/trunk/tutorial/websockets...
- newman314 14y agoOne of the things I've debated back and forth personally is if it's better to put nginx in front of varnish or vice versa. There are reasons to do either but I've not come up with a definitive reason to go one way or another.