Rules
ESA rules let you define conditions that control when specific feature configurations take effect.
Use rules to apply configurations for specific needs such as request transformation, content redirection, or cache policies. Rules also support fine-grained security and traffic management. All rules share consistent syntax to filter requests by characteristics and apply the matching configuration.
Simple configuration examples
Redirect requests by region
Rule configuration structure
When a request reaches an ESA node, ESA filters and processes it based on your rule configuration.
Every ESA rule configuration includes two parts:
Rule configuration = Rule expression + Action
Configure a rule expression to filter requests and an action to run on matched requests. The expression syntax is consistent across all rule-related features in ESA, so you can reuse configurations across features. Rule expression structure.
Feature availability by plan
Feature category | Feature | Free | Basic | Standard | Advanced | Enterprise |
Maximum nested sub-conditions per rule | 10 | 10 | 15 | 20 | 20 | |
Regular expression operator | ||||||
SSL/TLS rule, HTTPS rule (shared quota) | 5 | 10 | 50 | 75 | 125 | |
5 | 10 | 25 | 50 | 125 | ||
URL rewrite, modify outbound request header, modify outbound response header (shared quota) | 5 | 10 | 50 | 75 | 125 | |
5 | 10 | 50 | 75 | 125 | ||
cache eligibility, browser cache TTL, edge cache TTL, status code cache TTL, custom cache key (shared quota) | 5 | 10 | 50 | 75 | 125 | |
5(WebSocket configuration is not currently supported) | 10 | 50 | 75 | 100 | ||
file compression, image optimization, video processing (shared quota) | 5 | 10 | 50 | 75 | 100 | |
Maximum rules | 5 | 10 | 50 | 75 | 125 | |