All Products
Search

This Product

    Edge Security Acceleration:Configure protocol optimization

    Document Center

    Edge Security Acceleration:Configure protocol optimization

    Last Updated:Mar 31, 2026

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

    Background information

    HTTP/2

    HTTP/2 is the latest version of the HTTP protocol, succeeding HTTP/1.1. It introduces modern features such as binary framing, multiplexing, and header compression. These features significantly improve web performance and reduce transmission delay.

    HTTP/3 (QUIC)

    QUIC (Quick UDP Internet Connections) is a transport-layer network protocol. It provides security comparable to TLS/SSL and delivers lower connection and transmission delay. QUIC runs over UDP and delivers excellent performance in poor network conditions. It maintains active service even under severe packet loss or high network latency. QUIC implements congestion control algorithms at the application layer and does not require operating system or kernel support. This design offers greater flexibility for customization compared to traditional TCP protocols. It is ideal for businesses where TCP protocol 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 Site Management. 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 also provides good compatibility.

        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.

      • HTTP/3 (QUIC): Because HTTP/3 (QUIC) uses the UDP-based QUIC protocol, it establishes connections faster and delivers more stable Data Transmission Service 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. If you want to enable this feature only for specific requests, use rule configurations. Rule conditions identify specific parameters in user requests, enabling precise control over which requests the rule configuration applies to.

    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)