Edge Security Acceleration:Cache

Feature

Description

Default cache rules

Edge Security Acceleration (ESA) caches static resources from the origin server at the point of presence (POP) nearest to each client, reducing latency. Each POP includes a caching component. When a request or origin response passes through a POP, the component caches origin resources and assigns a time-to-live (TTL).

Feature

Description

Development mode

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.

Browser cache TTL

Browser cache TTL controls how long browsers keep resources in their local cache. By default, ESA honors the origin's Cache-Control header. You can set a custom cache duration without changing your origin configuration.

Edge cache TTL

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.

Ignore query string

Configure how POPs handle query strings when generating cache keys. Stripping the ? and everything after ? lets URLs with different parameters share one cached copy, improving cache hit ratios and reducing page load time.

Sort query strings

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.

Feature

Description

Create cache rules

You can configure a unique cache policy for each cache rule to set different browser cache TTLs.

Configure POP cache TTL

To set a cache time-to-live (TTL) for specific requests, such as those based on file extensions or request header features, you can create custom rules. This lets you configure cache settings that are different from the global edge cache TTL policy.

Configure cache TTL for status codes

When an origin server returns a non-2xx status code, Edge Security Acceleration (ESA) points of presence (POPs) can cache the status code and respond directly to subsequent requests within the cache validity period. This reduces repeated origin requests and lowers the load on the origin server.

Custom cache key

Define rules based on query strings, HTTP headers, or cookies to generate custom cache keys that unify the cache identity for similar requests, improving hit rates and reducing response time and bandwidth consumption.

Feature

Description

Purge cache

Cache purging clears cached resources from points of presence (POPs), forcing them to retrieve the latest content from your origin server. Purging many resources at once increases origin server load.

Prefetch content

The prefetch feature caches origin server resources on Edge Security Acceleration (ESA) POPs so that first-time requests are served from the edge without returning to the origin, improving cache hit ratio.

Feature

Description

Tiered cache

Edge Security Accelerator (ESA) caches origin server resources on globally distributed nodes at different tiers, delivering content from the nearest location to reduce latency and origin load.

Cache reserve

Cache reserve reduces origin traffic by consolidating origin requests through a top-level cache POP. ESA routes requests through this POP, which provides persistent storage to prevent less popular files from being evicted by frequently accessed content.