Hacker News Reader

Varnish 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...

One 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.

Node Http Proxy: https://github.com/nodejitsu/node-http-proxy

No need for Varnish for proxying your websockets.

Thanks 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.