4 ms·
Websockets run on port 80 natively. It's all done through a HTTP Upgrade header to turn the connection into a websocket. Up until this release, anyone running
by elliotanderson 14y ago
Websockets run on port 80 natively. It's all done through a HTTP Upgrade header to turn the connection into a websocket.
Up until this release, anyone running both HTTP and WebSockets behind nginx has had to run them on separate ports (i.e. HTTP = 80, WS = 8080) and then use TCP proxying to load balance the websocket connections. Nginx didn't natively understand the Upgrade header - but now it does so you're free to use port 80 for everything.