このページは現在英語版のみで提供されており、日本語版も近日中に提供される予定です。ご利用いただきありがとうございます。

HTTP Restrictions

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.
Request URL length
It is currently unrestricted, but will be restricted to 8192 B in the future.
Request body length
Upper limit of UInt64.
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.