tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary

WS/WSS Protocol Support

PDF
Focus Mode
Font Size
Last updated: 2026-03-23 10:08:28

What is WS/WSS?

WebSocket (WS) is a protocol that provides full-duplex communication channels over a single TCP connection.
WebSocket facilitates data exchange between the client and server, and allows active data push from the server to client. In WebSocket API, only one handshake is required between the browser and server to create a persistent connection and carry out bi-directional data transmission.

Why should WS/WSS be used?

Without WebSocket, the client has to pull data from the server through polling. There are two shortcomings in this data exchange method:
1. Low efficiency. To pull real-time data, the client has to frequently initiate the Ajax request.
2. The server cannot push data proactively. WebSocket is designed to solve these problems. As a new protocol released when HTML5 was launched, WebSocket achieves full-duplex communication between the browser and server. It can transmit message-based text and binary data, solving HTTP problems at the protocol level.
Key advantages of WebSocket:
1. Less overhead. After the connection is established, the packet header used for control is small. Compared to an HTTP request that requires a complete header, WebSocket helps reduce the overhead.
2. Real-time push. As a full-duplex protocol, WebSocket can achieve real-time data push from server to client.
3. Persistent connection.

How is WS/WSS billed?

CLB supports WS/WSS by default and no additional fees will be charged.

How do I enable WS/WSS for CLB?


WS
/WSS is enabled for CLB by default. If a connection is idle for more than 60s, you need to customize the proxy_read_timeout parameter, which should be less than 900s preferably. For more information, see Layer-7 Custom Configuration.
If the listener listens to HTTP or TCP SSL, WS is supported by default. If it listens to HTTPS, WSS is supported by default.
When WSS is used, CLB will carry out SSL offloading.
If the listener is configured for HTTPS or TCP SSL, WSS is supported by default. CLB will complete SSL offloading before forwarding the traffic.

Which regions support WS/WSS?

Currently, WS/WSS protocols are supported in all regions.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback