4 ms·
And for most corporations like mine to stop blocking websockets. What do you mean let some odd port through the firewall?
by twistedpair 14y ago
And for most corporations like mine to stop blocking websockets. What do you mean let some odd port through the firewall?
- mateuszf 14y agoHow about serving it using SSL on port 443?
- infamouscow 14y agoWebSockets over SSL (wss://) work just fine. Faris Chebib provided a nginx config file in #nginx earlier today. https://gist.github.com/octaflop/4991052 https://gist.github.com/octaflop/4991052
- elliotanderson 14y agoWebsockets 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.
- ef4 14y agoThat's the beauty of this nginx feature. Up until now, the easiest way to add websockets to an existing application was to put them on a separate (weird) port. But now nginx lets you multiplex those websocket connections over good old port 80 or 443, while still supporting regular HTTP(S) on those ports at the same time.