Purge CDN Cache
Last updated
Last updated
This feature allows admins to purge CDN caches at various scopes:
The entire planet
Specific domain(s) within the planet
Specific paths within domain(s)
A history of current and past activity is provided.
This feature is available when there is at least one CDN set up in the system. (To do this, contact customer support.) If no CDN is currently configured, an error message will be shown.
Purging requires these steps:
Select the cache(s)
Initiate the purge
(Optional) monitor the results
Cache selection is performed as follows.
At the top left of the page, ensure that All domains in the planet is selected, then skip the remainder of Step 1, and continue to Step 2 below.
At the top left of the page, ensure that Specific domains is selected. Additional controls will appear:
Select CDN: If there are multiple AWS load balancers, this control will appear. Select the AWS CDN provider for each domain/path where the cache has to be purged. In other situations (e.g., the planet uses the Google Cloud or Link11 CDN, or has only one AWS load balancer) this control is unnecessary and will not appear.
Host: Specify a domain configured within the planet.
Add Specific Path:
When this control is untoggled, caches for all paths within the specified domain will be purged.
When this control is toggled, the Add Path field will appear. Enter the path for which the cache should be purged.
Adding more domains/paths After appropriate values have been entered into the controls described above, if another domain or path purge needs to be defined, select the New Host button and populate the new entry in the purge list. Repeat this process until all desired purges have been specified.
Select the Purge CDN cache button. The specified purge(s) will appear in the Results list at the bottom of the page.
The Results list shows a history of purge commands submitted during the previous week. The list shows the date and time when each was submitted.
Within the list, the Status field shows the result of each purge during the most recent status update. Updates occur when the page is loaded or reloaded, and also each time the Refresh Status button is selected.
The possible statuses are:
In progress: as of the most recent status update, the purge was still being processed. (Note that depending on how recently the list was updated, the actual current status might be different.)
Done. The purge completed successfully.
Failed. The purge was attempted but was not successful. To try again, a new purge command must be submitted.
Not available. The purge was unsuccessful because the CDN was unavailable. To try again, a new purge command must be submitted.
