tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary
DocumentationCloud Load BalancerFAQsHTTP/2 Protocol Support

HTTP/2 Protocol Support

PDF
Focus Mode
Font Size
Last updated: 2024-01-04 14:39:00
Product Introduction
What is HTTP/2?
Why should I use HTTP/2?
Product Purchase
How does the billing work?
Product Implementation
How do I enable HTTP/2 on CLB?
Which regions support HTTP/2?

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.

Previous Topic: WS/WSS Protocol SupportNext Topic: Default Domain Name Blocking Prompt

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback