tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery（Beta）
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentationTencent Cloud EdgeOneGeneral ReferenceRequest and Response ActionsHTTP Restrictions

HTTP Restrictions

PDF
Focus Mode
Font Size
Last updated: 2025-01-24 15:09:12
This document will introduce the restrictions of EdgeOne on HTTP requests/responses in various dimensions and the response behaviors once these restrictions are exceeded.
Restriction Item
Description
Request header length (key + value)
The total size of the request header name and header value is restricted to 128 KB. If exceeded, the EdgeOne node will respond with a 413 status code.
Response header length (key + value)
The total size of the response header name and header value is restricted to 128 KB. If exceeded, the EdgeOne node will respond with a 413 status code.
Number of HTTP request headers
The total number of HTTP request headers is 256.
HTTP/1.1 requests: If exceeded, the EdgeOne node will respond with a 400 status code.
HTTP/2.0 requests: If exceeded, the EdgeOne node will send goaway and close the stream.
Number of HTTP response headers
The total number of HTTP response headers is 256.
HTTP/1.1 requests: If exceeded, the EdgeOne node will respond with a 400 status code.
HTTP/2.0 requests: If exceeded, the EdgeOne node will send goaway and close the stream.
Size of the header key or value for HTTP/2 requests
The size of a single header name or value is restricted to 32 KB. If exceeded, the EdgeOne node will send goaway and close the stream.
Maximum number of requests per HTTP/2 stream
Maximum number of requests per stream is 1000, no limit on origin requests.
aximum concurrency per HTTP/2 stream
Maximum concurrency per stream is 128
Request URL length
It is currently unrestricted, but will be restricted to 8192 B in the future.
Request body length
Upper limit of UInt64.
For the POST request upload body length limit, please refer to Maximum Upload Size.
Response body length
Upper limit of UInt64.
Cache size
It is currently unrestricted, but will be restricted to 30 GB in the future.
Request method
The supported methods only include GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT, OPTIONS, PATCH, COPY, LOCK, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK. For requests with other methods, the EdgeOne node will directly respond with a 400 status code.



Previous Topic: Default HTTP Response HeadersNext Topic: Country/region and Corresponding Codes

Help and Support

Was this page helpful?

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

Feedback