Cache eligibility

更新时间:
复制 MD 格式

To bypass the Edge Security Acceleration (ESA) cache for resources that match the default cache rule, create a rule to filter requests and set Cache Eligibility to Bypass Cache.

Note

If no cache rules or configurations are set, caching on 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 bypass cache rule for those resources. Bypassing the cache for dynamic resources improves access performance.

Procedure

  1. In the ESA console, you can choose Site Management. In the Website column, you can click the target site.

  2. In the navigation pane on the left, choose Rules > Cache Rules.

  3. Click Create Rule and enter a Rule Name.

  4. 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.

  5. In the Cache Eligibility area, select a cache policy and click OK.

    image

    • Bypass Cache: All requests skip the POP cache and fetch directly from the origin, allowing you to view the latest resources from the origin server in real time. When enabled, only the Browser Cache TTL setting applies.

    • Eligible for Cache: All eligible requests are served from POP cache nodes instead of the origin. This avoids long origin fetch paths, reduces latency, and improves access performance.

Related documentation

Rule-related features vary in effective priority, reentrancy, and effective granularity. For details, see Properties of Rule-Related Features.