You can purge all resources cached for your website. However, for a website with heavy traffic and an extensive number of files cached on Edge Security Acceleration (ESA) points of presence (POPs), purging all cache may result in a significant increase in origin requests and downgraded website performance.
This operation cannot be undone. Use it with caution.
Scenarios
Large-scale update of website content
Replacement or redeployment of an entire website
Unknown cache pollution
Purge all cache
In the ESA console, choose Websites. In the Website column, click the target website.
In the left navigation pane, choose .
On the Purge Cache tab, configure the purge settings.
Type: Select Purge All Cache.
Purge Method: Select Mark as Expired or Delete.
Mark as Expired
If the requested content is one of the resources that you submit to purge, the nearest POP checks the Last-Modified parameter of the resource on the origin server. If the parameter value is the same as that of the cached resource, the POP serves the cached resource. Otherwise, the cached resource is considered expired. In this case, the POP fetches the latest version from the origin server, delivers it to the client, and updates the cache with the new version.
Delete
If the requested content is one of the resources that you submit to purge, the nearest POP fetches the latest version from the origin server, delivers it to the client, and updates the cache with the new version.

Click Submit.
View the purge progress.
You can view the progress and details of a purge task on the Operation Records tab. The purge task is complete when the progress reaches 100%. The progress varies based on the number of objects that you want to purge.
Availability
Quota | Entrance | Pro | Premium | Enterprise |
Purge tasks per day | 50 | 80 | 125 | 200 |