Applications limits
Check the bounds of an Application, its rules and settings, and of the Cache, Application Accelerator, and Image Processor settings it carries.
An Application processes the requests received by your Workloads: it runs its request and response rules on each request. With WebSocket Proxy turned on for the account, it can also proxy WebSocket connections to the origin. An Application receives the requests of a Workload once that Workload’s deployment sets that Application.
Each Platform Resource turned on in the Application adds bounds of its own. Cache bounds cache settings and the objects it stores, and Real-Time Purge bounds purge requests. Application Accelerator moves the floor of the cache time to live (TTL), and Image Processor bounds the size, width, and height of one image. This page states each bound and the answer a call receives where the API refuses it.
A service plan also includes an amount of usage before a rate applies. That amount is a billing quantity: passing it changes what the account is charged rather than what the call returns. Azion pricing lists the plans and the usage each one includes. For the rates, refer to Pricing.
Applications, rules, and connections
These bounds apply to every Application, whichever Platform Resources are turned on in it. They cover the rules in its Rules Engine, the Debug Rules log, and the connections it keeps open.
Default limits
Seven bounds apply to every Application.
| Scope | Limit |
|---|---|
| Rules in one Application, request and response phases together | 200 rules |
| Criteria groups per rule | 1 to 5 groups |
| Criteria per group | 1 to 10 criteria |
| Behaviors per rule | 1 to 10 behaviors |
| Behavior argument | 1,600 characters |
| Debug Rules log size | 1.5 kB |
| WebSocket connection time | 15 minutes |
Three further bounds apply to names: an Application’s name takes 1 to 100 characters, a device group’s name takes 1 to 250, and a device group’s user_agent expression takes 1 to 512.
The 200 rules are one total that the request phase and the response phase share. For example, an Application can carry 150 request rules and 50 response rules, but not 200 of each.
Azion recycles the keepalive connections on its servers approximately every 15 minutes. That cycle bounds how long a connection between a user and an Application stays open. An active connection that needs more time can be terminated. When a WebSocket connection closes this way, your client code has to detect the closed connection and open it again.
For a large file, either of two options lets each transfer finish before the connection is recycled. With modules.cache.large_file_cache.enabled set to true in a cache setting, Cache stores the file in fragments of 1,024 kB. The other option, compression, shrinks the file.
To store a large file in fragments, refer to Cache settings. To compress it, refer to Compress application responses with gzip.
Cache
Cache bounds a cache setting and an object it stores, and Real-Time Purge bounds a purge request. Past a bound that the API checks, the call returns HTTP 400 with an error code and a title. Tiered Cache changes two bounds of a cache setting: the lowest TTL it takes and the cache behavior it allows.
The API validates the TTL bounds on every cache setting.
For the rates of Cache, refer to Pricing. To query the data that Tiered Cache transferred, refer to Query usage data from Tiered Cache.
Cache settings
Each bound in this table applies to one cache setting, from any interface that writes it. The Scope column names the API field and, where one exists, the Console label. The Past the limit column carries the code and the title of the 400 answer. The error titles keep earlier names: Edge Cache stands for Cache, and Module stands for a Platform Resource turned on in the Application.
| Scope | Limit | Past the limit |
|---|---|---|
Cache TTL minimum, Max Age (modules.cache.max_age) |
60 seconds; 0 seconds with Application Accelerator on the Application | Error 21021, Edge Cache Max Age Lower Than The Minimum Allowed By Application's Application Accelerator Module, with meta.min_value set to 60. |
| Cache TTL minimum with Tiered Cache on | 3 seconds, with Application Accelerator on; without it, the 60-second minimum holds | Error 21020, Edge Cache Max Age Lower Than The Minimum Allowed By The Tiered Cache Module, with meta.min_value set to 3. |
| Cache TTL maximum | 31,536,000 seconds, one year | Error 10068, Max Value, with the detail Ensure this value is less than or equal to 31536000. |
Cache behavior with Tiered Cache on (modules.cache.behavior) |
override only |
Error 21001, It's Not Possible To Use This Edge Cache Behavior. |
Browser cache TTL (browser_cache.max_age) |
0 to 31,536,000 seconds | Error 10068, Max Value. |
Cache setting name, Name (name) |
250 characters | Error 10046, Max Length, with the detail Ensure this field has no more than 250 characters. |
One further bound applies to a cache setting: its cache_vary_by_method array takes at most 2 values, post and options.
With modules.cache.stale_cache.enabled set to true in a cache setting, Cache can serve an expired copy of an object for a limited window. Under the honor behavior, the window is the value of the origin’s stale-while-revalidate=<ttl> directive. Under override, or when the origin omits the directive, the window is 300 seconds.
Cached objects
Two bounds apply to an object that Cache stores: its size, and the size of each fragment of a large file stored in pieces. The API checks the fragment size on every cache setting.
| Scope | Limit | Past the limit |
|---|---|---|
Fragment size of a large file (modules.cache.large_file_cache.offset) |
1,024 kB per fragment, fixed | Error 10068, Max Value, with the detail Ensure this value is less than or equal to 1024. |
A single object in cache takes up to 10 GB.
Real-Time Purge
Each bound in this table applies to a purge request, from any interface that sends one. The Past the limit column carries what the API returns past the bound.
| Scope | Limit | Past the limit |
|---|---|---|
| Objects in one URL or cache key purge request | 50 objects | Error 10065, List Field Max Length, with the detail Ensure this field has no more than 50 elements. |
| Wildcards in one purge request | 1 wildcard | Error 10065, List Field Max Length, with the detail Ensure this field has no more than 1 elements. |
A URL or a cache key in a purge takes up to 4,096 characters.
Six more bounds set the rate of purge requests, the length of a wildcard, and how much purge history Azion keeps.
| Scope | Limit |
|---|---|
| URL and cache key purge requests per client | 200 requests, 50 objects each |
| Objects purged by URL and cache key every 60 seconds | 10,000 objects |
| Wildcard purge requests per day, in a 24-hour interval | 2,000 requests |
| Wildcard length | 256 characters |
| Requests kept in the purge history | 1,000,000 requests |
| Time a request stays in the purge history | 6 months |
Application Accelerator
Application Accelerator changes one bound of a cache setting: the shortest time Cache holds an object. The Max Age of a cache setting, its modules.cache.max_age field, sets in seconds how long Cache holds an object. The field takes an integer from 0 to 31,536,000 and refuses any value outside that range. Whether Application Accelerator and Tiered Cache are on decides how low inside the range a cache setting goes.
For the rates of Application Accelerator, refer to Pricing.
Default limits
Each row names a cache TTL bound and the condition that puts it in force.
| Scope | Limit | Applies when |
|---|---|---|
| Minimum cache TTL | 60 seconds | Application Accelerator is off in the Application, with Tiered Cache on or off. |
| Minimum cache TTL | 0 seconds | Application Accelerator is on, and Tiered Cache is off. |
| Minimum cache TTL | 3 seconds | Application Accelerator is on, and Tiered Cache is on. |
| Maximum cache TTL | 31,536,000 seconds, one year | Every cache setting, whichever Platform Resources are on. |
A Max Age lower than the minimum in force returns HTTP 400. The error is 21021 while Application Accelerator is off, and 21020 while Application Accelerator and Tiered Cache are both on. A value higher than the maximum returns error 10068. For the error titles, refer to Cache settings.
For how a Max Age of 0 seconds and the Bypass Cache behavior each handle a request, refer to Bypass Cache and a TTL of 0.
A request that Application Accelerator varies is still bounded by the Platform Resources that store the object and run code on it. Cache bounds the object itself: the size of one cached object, and the size of each fragment of a large file. For those values, refer to Cached objects. A Function that the Application runs carries its own limits on its code and on each invocation. For those values, refer to Functions limits.
Image Processor
Image Processor bounds a single image with three default limits: its size, its width, and its height.
For the rates of the Images metric, refer to Pricing. To query the number of images the account has processed, refer to Query usage data from Image Processor.
Default limits
Image Processor applies three default limits to an image: a maximum size of 150 MB, a maximum width of 3,840 pixels, and a maximum height of 2,160 pixels.
Each ims parameter also accepts a range of values of its own. For the range of each parameter, refer to URL parameters.