Edgio sets limits on requests, responses, and access logs.
Data storage units are defined below.
Kbstands for kilobytes and means 1,024 bytes (2^10 bytes)
Mbstands for megabytes and means 1,024 kilobytes (2^20 bytes)
Gbstands for gigabytes and means 1,024 megabytes (2^30 bytes)
Edgio requires that all requests and responses meet the following requirements:
|Response time from origin server||60 seconds||The maximum number of seconds that Edgio will wait for a response from an origin server (e.g., your web server). The response for a request that exceeds this limit is a 536 Project HTTP Response Timeout.|
|Response body size from static||2Gb||The maximum size of a response body of Edgio static assets.|
|Response body size from custom origin||2Gb||The maximum size of a response body from a custom origin.|
|Response body size from Edgio cloud||6Mb||The maximum size of a response body from the Edgio cloud.|
|Path and query string size||8Kb||The maximum bytes (not characters) that Edgio will accept in path and query string.|
|Cookie size||32Kb||The maximum bytes that Edgio will accept in request or response cookies.|
|HTTP header size||64Kb||The maximum bytes that Edgio will accept in request or response HTTP headers.|
|HTTP header count||70||The maximum number of developer-controlled headers Edgio will accept in HTTP request or response. Exceeding this will result in 542 status code.|
|Scheduling timeout||60 seconds||The number of seconds Edgio will try to schedule a request processing before timing out. Exceeding this will result in 541 status code.|
|Worker timeout||20 seconds||The number of seconds Edgio will wait for project code to process the request before timing out. Exceeding this will result in 539 status code.|
|Total number of prerendered requests||25,000 per deployment|
|Maximum number of nested requests||3||“Nested” means an Edgio site is the upstream of itself or of another Edgio site. Exceeding this will result in 538 status code.|
The following headers are served for use by Edgio. You may not modify these request headers.
- All header names that start with
RTLD limitations are described below.
|Time||3 days||If our service is unable to deliver log data, then we will store it for up to 3 days and deliver it when communication resumes. If we cannot deliver log data within 3 days, then it will be permanently deleted.|