All Products
Search

This Product

    Edge Security Acceleration:Configure protocol optimization

    Document Center

    Edge Security Acceleration:Configure protocol optimization

    Last Updated:Jun 15, 2026

    After you enable SSL/TLS and configure the site certificate, Edge Security Acceleration (ESA) automatically enables HTTP/2 and HTTP/3 (QUIC).

    Background information

    HTTP/2

    HTTP/2 succeeds HTTP/1.1 with binary framing, multiplexing, and header compression, significantly improving web performance and reducing transmission delay.

    HTTP/3 (QUIC)

    QUIC (Quick UDP Internet Connections) is a UDP-based transport-layer protocol that provides TLS/SSL-level security with lower connection and transmission delay. It performs well in poor network conditions, maintaining active service even under severe packet loss or high latency. QUIC implements congestion control at the application layer without requiring OS or kernel support, offering greater flexibility for customization than traditional TCP. It is ideal for scenarios where TCP optimization faces bottlenecks.

    Notes

    • The maximum concurrent connections for HTTP/2 on ESA is 128. If you require more concurrent connections, disable HTTP/2 access and instead use HTTP/1.1 or HTTP/3 (QUIC).

    • ESA supports IETF QUIC and Google QUIC. Google QUIC supports versions Q39, Q43, or Q46.

      • IETF QUIC is the Internet standard version.

      • IETF QUIC is compatible with Google QUIC versions Q39, Q43, and Q46. Use IETF QUIC.

    Procedure

    1. In the ESA console, select Websites, and in the Website column, click the target site.

    2. In the navigation pane on the left, choose Speed and Network > Optimize.

    3. On the Speed and Network page, click the Speed Optimization tab. As needed, enable the HTTP/2, HTTP/2 to Origin, or HTTP/3 (QUIC) switch.image

      • HTTP/2: Based on existing HTTPS, HTTP/2 uses multiplexing and header compression to improve website performance and resource loading speed. It is also widely compatible.

        Note

        • This configuration applies to all domain names under the site. If you want to enable HTTP/2 to Origin only for specific domain names, add rules for those domain names. For more information, see Network Optimization Rules.

        • The HTTP/2 protocol and the WebSocket protocol cannot take effect in the same connection. Do not enable both at the same time.

      • HTTP/3 (QUIC): Because HTTP/3 (QUIC) uses the UDP-based QUIC protocol, it establishes connections faster and delivers more stable data transmission in unstable or mobile network environments.

    Correspondence between global site features and rule-based features

    Global site configurations apply to all requests under the site. To apply this feature only to specific requests, use rule configurations. Rule conditions match parameters in user requests, enabling precise control over which requests are affected.

    Global Site Feature

    Corresponding Rule Feature

    HTTP/2

    HTTP/2

    HTTP/2 back-to-origin

    HTTP/2 back-to-origin

    HTTP/3 (QUIC)

    HTTP/3 (QUIC)