Purge cache

How cache purging works

Cache purging marks resources on all Edge Security Acceleration (ESA) POPs as expired. When a user requests a purged resource, ESA retrieves the latest version from the origin server. ESA returns it to the user and re-caches it on the POP. This reduces the cache hit ratio.

Scenarios

• Update and publish resources

  After updating resources on your origin server, submit their URLs or directories for purging. This ensures users access the latest content from ESA POPs.

• Remove illicit content

  Illicit content removed from your origin server may still be served from ESA POP caches. Purge the affected resources to remove them from all POPs.

Usage notes

• After a successful purge, cached resources on ESA POPs become invalid. POPs retrieve purged resources from the origin server on the next request and re-cache them. Submitting many purge tasks at once spikes origin bandwidth and increases origin server load.

• A purge task takes about 5 to 6 minutes to take effect. If a resource has a cache TTL of less than 5 minutes, no purge is needed — the cache expires on its own.

• If the URI contains non-ASCII characters (such as Chinese characters or special characters) or reserved characters (such as spaces), encode the URI before submitting the purge task.

Support by plan