Cloud Load Balancer
- Release Notes and Announcements
- Product Introduction
- Product Comparison
- Purchase Guide
- CLB Resource Package
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- Real Server
- Health Check
- Certificate Management
- Log Management
- Monitoring and Alarm
- Cloud Access Management
- Practical Tutorial
- Obtaining Real Client IPs
- Ops Guide
- Troubleshooting
- API Documentation
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- CLB API 2017
- Making API Requests
- Request Structure
- Returned Results
- General APIs
- Classic CLB APIs
- APIs for CLB Instances
- APIs for Listeners
- CLB Real Server APIs
- APIs for Health Check
- FAQs
- Troubleshooting Health Check Issues
HTTP/2 Protocol Support
Last updated: 2024-01-04 14:39:00
Product Introduction
Product Purchase
Product Implementation
What is HTTP/2?
HTTP/2 (Hypertext Transfer Protocol Version 2) is a major revision of the HTTP network protocol used by the World Wide Web.
HTTP/2 is designed to address the performance issues in HTTP1.X to better use network resources and reduce network application latency.
HTTP/2 is backward compatible with HTTP1.X.
Why should I use HTTP/2?
Compared with HTTP1.X, HTTP/2 can make the response be more fast and efficient. HTTP/2 has the following advantages:
Multiplex: concurrent processing brings a faster response.
Server push: the server proactively pushes resources needed by the client, reducing the number of requests.
More features include bandwidth limit, request priority, header compression, and binary framing.
How does the billing work?
CLB supports the HTTP/2 protocol without charging extra fees.
How do I enable HTTP/2 on CLB?
Note：
The HTTP listener does not support HTTP/2. Mainstream browsers and web servers only support the TLS-based HTTP/2 protocol.
The HTTP1.X protocol is still used between the CLB instance and the real server.
1. Enable HTTP/2 on HTTPS listeners
CLB instance: you can enable or disable the HTTP/2 protocol in a CLB instance. For more information, please see Configuring an HTTPS Listener.
Classic CLB instance: HTTPS listeners created for a classic CLB instance before April 2018 do not support HTTP/2. HTTPS listeners created after April 2018 support but cannot disable HTTP/2.
2. Agree on the protocol at client access
When the client accesses an HTTP/2-enabled listener, the protocol version will be negotiated during the handshake process of HTTPS. The client uses ALPN (Application-Layer Protocol Negotiation) to inform the server of a list of supported protocols. The server selects HTTP/2 or HTTP1.X according to the protocol list. If the client does not support HTTP/2, the server will be automatically backward compatible without requiring additional configuration.
Which regions support HTTP/2?
Currently, all regions support HTTP/2.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No