Product limits
Keep these limitations in mind when designing your EdgeWorkers functions. These limitations apply to all EdgeWorkers functions regardless of the selected resource tier.
You can also refer to the limitations that are applied based on the resource tier you selected for your EdgeWorker ID.
Description | Limit |
---|---|
Supported delivery products | Ion |
Supported delivery method | Enhanced TLS Standard TLS, used to serve non PCI compliant traffic over HTTP or HTTPS via an EdgeWorkers is not supported on âAkamaiâ CDNs created to accommodate unique regional or governmental requirements. This limitation currently includes China CDN. |
Execution restrictions | EdgeWorkers functions cannot be executed by an Edge Site Includes fragment request. |
Number of activated EdgeWorker scripts per account | 25,000 on the staging network |
Number of EdgeWorker scripts executed per request | 1 |
Compressed size for a code bundle | 512 KB |
Uncompressed size for a code bundle | 1 MB |
Maximum response header size for HTTP sub-requests | 8000 bytes |
Maximum body size for responses created through the | 2048 characters |
Maximum body size for responses from origin to an EdgeWorkers function, using | 128 KB when using 5 MB when using |
Maximum body size for responses from an EdgeWorkers function to a browser when the response is passed through as a string | 100,000 bytes if you pass a string to No direct limit if you pass a stream to |
Maximum body size for responses from an EdgeWorkers function to a client browser | 2048 characters if you use |
Maximum body size when | 16 KB |
JavaScript initialization timeout The JavaScript initialization time does not include the time it takes to fetch and decompress the EdgeWorkers code bundle. | 100 milliseconds |
JavaScript CPU initialization timeout | 30 milliseconds |
Updated 2 days ago