WebSocket is a connection protocol based on TCP. It is designed to transfer data between a client (e.g., a browser) and a server over a persistent TCP connection. A persistent connection only needs to be established once, and then data can be transmitted without breaking the connection or making additional requests. Such connections continue until one of the participants terminates it.
WebSocket is suitable for services that require constant data exchange, such as chat rooms, online games, real-time trading platforms, etc. For static or slowly updated data on a website (e.g., in a blog or product catalog), WebSocket connections could be more optimal. To receive updates, the client only needs to reload the page manually.
1. WebSocket protocol is bidirectional, which means that clients and servers can send data to each other anytime during the connection. HTTP protocol is unidirectional, as the server sends data only when it receives the client's request. With WebSocket, you can leave a page with a chat or social network open and receive messages when they are sent. If HTTP were used, you would have to refresh the page every time to see if a message arrived.
2. WebSocket establishes one connection and keeps it open permanently. HTTP establishes a new connection every time the client makes a request and breaks it after the server responds.
By default, the WebSocket feature is enabled for CDN resources created for the entire site and disabled for CDN resources created for only static assets. You can manage this feature depending on your concerns: disable it for the CDN resources with full integration or enable it for resources with partial integration.
To manage the WebSocket feature:
1. Go to the CDN section in the control panel and open the settings of the resource for which you want to manage WebSockets by clicking its custom domain.
The new page opens. Do the remaining steps on it.
2. Open the "Content" section and click Websockets.
3. Enable or disable the feature.
4. Save changes.
Was this article helpful?
Learn more about our next-gen CDN