gerglo.blogg.se

There are some challenges that a reverse proxy server faces in supporting WebSocket.

The HTTP Upgrade mechanism used to upgrade the connection from HTTP to WebSocket uses the Upgrade and Connection headers. For example, WebSocket applications can use the standard HTTP ports 80 and 443, thus allowing the use of existing firewall rules.Ī WebSocket application keeps a long‑running connection open between the client and the server, facilitating the development of real‑time applications. This allows WebSocket applications to more easily fit into existing infrastructures. The WebSocket protocol is different from the HTTP protocol, but the WebSocket handshake is compatible with HTTP, using the HTTP Upgrade facility to upgrade the connection from HTTP to WebSocket. (All releases of NGINX Plus also support WebSocket.)Ĭheck out recent performance tests on the scalability of NGINX to load balance WebSocket connections. Most modern browsers support WebSocket including Chrome, Firefox, Internet Explorer, Opera, and Safari, and more and more server application frameworks are now supporting WebSocket as well.įor enterprise production use, where multiple WebSocket servers are needed for performance and high availability, a load balancing layer that understands the WebSocket protocol is required, and NGINX has supported WebSocket since version 1.3 and can act as a reverse proxy and do load balancing of WebSocket applications.

Part of HTML5, WebSocket makes it much easier to develop these types of applications than the methods previously available. The WebSocket protocol provides a way of creating web applications that support real‑time bidirectional communication between clients and servers.