The QUIC protocol provides enhanced security for data transmission between clients and CDN edge nodes and also accelerates content delivery. This topic introduces QUIC and the billing rules, and describes how to enable QUIC.
What is QUIC?
QUIC is an experimental transport layer network protocol that provides the same security capabilities as TLS/SSL and reduces connection and transmission latency. QUIC is developed based on UDP and has excellent performance when network connections are weak. When packet loss and network latency issues are severe, QUIC can still ensure service availability. QUIC can implement different congestion control algorithms at the application layer regardless of the operating system or kernel that is used. Compared with TCP, QUIC supports flexible changes based on service requirements. QUIC is a suitable alternative when TCP optimization encounters bottlenecks.
QUIC supported by Alibaba Cloud CDN is implemented at Layer 7.
- IETF QUIC is a standard Internet protocol.
- IETF QUIC is compatible with gQUIC versions G39, Q43, and Q46. We recommend that you use IETF QUIC.
How it works
- If you use Google Chrome, the Alibaba Cloud CDN already supports the standard protocol of HTTP/3. Google Chrome can directly send QUIC requests to Alibaba Cloud CDN.
- If you use a self-developed app, the app must be integrated with a network protocol library such as lsquic-client, Cronet, ngtcp2, or quiche that supports QUIC.
Billing rules for QUIC
- Alibaba Cloud CDN identifies QUIC requests based on whether they are transmitted over UDP.
- QUIC requests whose header specifies QUIC: Alibaba Cloud CDN identifies whether the request is a QUIC request. If so, you are charged for a QUIC request. If not, you are charged for an HTTPS request.
How to identify QUIC requests
In the following example, Google Chrome is used to show how to identify QUIC requests.
The following figure shows that the Protocol column displays h3-29, which indicates that the request is a QUIC request.