The QUIC protocol helps you access applications faster and achieves multiplexing with no reconnection required in scenarios such as weak network or frequent switch between Wi-Fi and 4G. This document introduces how to configure QUIC protocol in the CLB Console.
Quick UDP Internet Connection QUIC 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:
After QUIC is enabled, the client can establish a QUIC connection with a CLB instance. If the QUIC connection fails due to negotiation between the client and the CLB instance, HTTPS or HTTP/2 will be used. However, the CLB instance and the real server still use the HTTP1.x protocol.
Currently, CLB supports QUIC Q044 and earlier versions.
When creating a CLB instance, select “Beijing”, “Shanghai” or “Mumbai” for Region, and “Public Network” for Network Type.
- If you enabled the QUIC protocol when creating a HTTPS fowarding rule, you can enable or disable the QUIC protocol later as needed. If you did not enable the QUIC protocol when creating a HTTPS forwarding rule, you cannot enable it later.
- Based on the UDP protocol, QUIC will use the UDP port of a CLB instance. If you enable QUIC for a HTTPS listener, UDP and TCP ports will be used. For example, you enable QUIC for the HTTPS:443 listener, both TCP:443 and UDP:443 ports are used, and you cannot create the TCP:443 or UDP:443 listener.