If you want Edge Security Acceleration (ESA) to bypass the cache for specific resources that would otherwise match the default cache rule, you can create a rule with conditions to filter these requests and set Cache Eligibility to Bypass Cache.
If no cache rules or configurations are set, the caching logic of ESA points of presence (POPs) follows the default cache rule.
Scenarios
If your origin server has resources that you do not want to cache on ESA POPs, such as dynamic resources where each request must fetch the latest content from the origin, configure a cache rule to use the bypass cache mode for these resources. Bypassing the cache for dynamic resources improves access performance.
Procedure
In the ESA console, you can choose Websites. In the Website column, you can click the target site.
In the navigation pane on the left, choose .
Click Create Rule and enter a Rule Name.
In the If requests match... section, set the request attributes to match. For more information about how to configure rules, see Composition of a rule expression.
In the Cache Eligibility area, select a cache policy and click OK.
Bypass Cache: All requests bypass the cache on points of presence (POPs), allowing you to view the latest resources from the origin server in real time. When Bypass Cache is enabled, only the Browser Cache TTL setting takes effect.
Eligible for Cache: All cache-eligible requests are routed through cache components on Points of Presence (POPs), allowing resources to be retrieved directly from cache nodes instead of the origin server. This process avoids long origin fetch paths, reduces latency, and improves resource access efficiency.
References
Rule-related features vary in execution priority, rule behavior, and configuration scope. For more information, see How ESA rules take effect.