You can create a QUIC listener to a CLB instance to forward encrypted QUIC requests from the client. For QUIC listeners, the real server can directly get the real client IP.
QUIC (Quick UDP Internet Connection) is a transport layer network protocol designed by Google, multiplexing concurrent data streams using UDP. Compared with the popular TCP+TLS+HTTP2 protocol, QUIC has the following advantages:
Establish a connection faster
Improve congestion control.
Adopt multiplex to avoid head-of-line (HOL) blocking.
Supporrt connection migration.
Use Cases
A QUIC listener supports connection migration. When your network changes, such as frequent switches between mobile and Wi-Fi networks, it can smoothly migrate the connections without interruption. This is suitable for audio/video services, game services, etc.
Restrictions
QUIC listeners are not available for classic CLB.
QUIC listeners are not available for CLBs deployed on the classic network.
Only IPv4 and IPv6 NAT64 CLB instances support the QUIC listener.
1. Log in to the CLB console and click Instance Management on the left sidebar.
2. Select a region in the top-left corner of the CLB instance list page and click Configure Listener in the Operation column on the right.
3. Under TCP/UDP/TCP SSL/QUIC Listener, click Create and configure the QUIC listener in the Create Listener pop-up window.
3.1 Basic Configuration
Configuration Item
Description
Example
Name
Listener name.
test-quic-443
Listener Protocol and Ports
Listener protocol: Select QUIC. CLB can receive QUIC requests made by clients, but TCP is still used between CLB and real server.
Listener port: It’s used to receive requests and forward them to the real server. Port range: 1-65535.
The listener port must be unique in the same CLB instance.
QUIC:443
SSL parsing
One-way authentication and mutual authentication are supported.
One-way authentication
Server certificate
You can select an existing certificate in the SSL certificate console or create a certificate.
Existing certificate
Balancing method
For QUIC listeners, CLB supports two scheduling algorithms: weighted round robin (WRR) and weighted least connections (WLC).
WRR: Requests are sequentially delivered to different real servers according to their weights. Scheduling is done based on the number of new connections, where servers with higher weights will undergo more polls (i.e., a higher probability), while servers with the same weight process the same number of connections.
WLC: Loads of servers are estimated according to the number of active connections to the servers. Scheduling is done based on server loads and weights. If their weights are the same, servers with fewer active connections will undergo more polls (i.e., a higher probability).
Yes
No
Was this page helpful?