You can configure a global cache policy to cache static resources on points of presence (POPs). This increases resource hit rates, improves client access performance, and reduces back-to-origin traffic.
Feature | Description |
You can specify whether points of presence (POPs) ignore the question mark ( | |
Browser cache time-to-live (TTL) defines how long resources (such as HTML, CSS, JavaScript files, and images) are stored in the local browser cache. By default, it follows the | |
The edge cache time-to-live (TTL) is the period of time during which origin resources are cached on Edge Security Acceleration (ESA) points of presence (POPs). When the TTL ends, resources that are cached on POPs are marked as expired. If the requested resource has expired on a POP, the POP retrieves the most recent resource from the origin server and caches it. You can configure a cache TTL for static resources based on file directories or file name extensions. This reduces the load on the origin server and improves access performance. | |
Enable development mode to ensure that clients can immediately retrieve the latest static resources. When this mode is enabled, static resource requests temporarily bypass the caching components of Edge Security Acceleration (ESA) and are forwarded directly to the origin server. This lets you verify changes to your origin content. | |
When you enable the query string sorting feature, Edge Security Acceleration (ESA) automatically sorts the query string parameters in a URL when processing a request. ESA then uses the sorted query string to look up content in the cache or forward the request. This means that a point of presence (POP) treats requests as being for the same file if the parameters and their values are identical, regardless of their order in the URL. This feature helps improve the cache hit ratio. |
Site-leval and feature-based rules mapping
Configurations for site global features apply to all requests for the site. If you want to enable a feature for only specific requests, use rule features. You can use rule conditions to detect specific parameters in user requests. This allows for more precise control and ensures that rule configurations apply only to specified requests.
Site-level | Corresponding feature-level rules |
Query string | |
Query string sorting | |
Browser cache time-to-live (TTL) | |
Edge cache time-to-live (TTL) | |
Cache reserve |