Global cache configuration
Configure a global cache policy for static resources. This caches static resources at edge nodes to improve cache hit rates, accelerate client access, and reduce back-to-origin traffic.
If you do not set any cache rules or cache configurations, the caching logic of Edge Security Acceleration (ESA) POPs follows the default cache rule.
|
Feature |
Description |
|
Configure how POPs handle query strings when generating cache keys. Stripping the |
|
|
Browser cache TTL controls how long browsers keep resources in their local cache. By default, ESA honors the origin's |
|
|
Edge cache TTL controls how long Edge Security Acceleration (ESA) PoPs cache origin resources. When a client requests a stale resource, the ESA PoP retrieves the latest version from the origin and caches it again. Set TTL for static resources by directory or file extension to reduce origin load and speed up delivery. |
|
|
When enabled, development mode temporarily bypasses the caching components of Edge Security Acceleration (ESA) and forwards all static resource requests directly to your origin server, so you can verify content changes in real time. |
|
|
Query string sorting makes Edge Security Acceleration (ESA) sort URL parameters before cache lookup or request forwarding. Requests with identical parameters are treated as the same resource regardless of parameter order, which improves the cache hit ratio. |
Mapping between site-level features and rule-based features
Settings added under site-level global features apply to all requests for that site. To apply a feature only to specific requests, use rule-based features. Define conditions in your rules to detect specific parameters in user requests. This gives you precise control over which requests the rule applies to.
|
Site-level feature |
Corresponding rule-based feature |
|
Query String |
|
|
Query String Sorting |
|
|
Browser Cache Time-to-Live (TTL) |
|
|
Edge Cache Time-to-Live (TTL) |
|
|
Cache Reservation |