The portal allows you to perform cache purges for resources in your configured domains. Select Config > Cache Purge from the left navigation pane to display the Cache Purge screen.
|Note||If purging the cache is disabled for the logged-in user on this property, a message to that effect is displayed.|
To purge the cache, first select the specificity of the purge you want to perform. The choices are
- Multiple URLs
- Single URL
- Complete domain
We'll consider these in order of simplicity.
To purge a complete domain:
Select Complete domain, and select the domain you want to purge from the pulldown. (Properties with only a single domain already have that domain selected.)
To purge a single URL:
Select Single URL, and select the domain you want to purge from the pulldown. Enter the path of the object you want to purge:
If you want to purge full directories (a prefix purge), use an asterisk; for example, images/* will purge all cached objects that are from the /images directory of the selected domain:
Note that if you do not specify a path or prefix, the entire selected domain's contents will be purged from the cache. This might take several minutes to complete.
|Note||Occasionally you might encounter a situation where you have some specific objects you want to purge from the cache, but when the cache purge command is sent, the old objects are still in the cache and being returned to requests.
If your configuration rewrites any URLs for some reason, the corresponding objects are placed in the cache based on the post-rewrite URLs. But you are using pre-rewrite URLs to purge objects. This mismatch results in Instart reporting back that pages are purged, but in reality the objects are still present in the cache.
If this happens to you, please contact Support and they can see if there is a rewrite in effect that is changing the object's URL, and issue a purge request with the proper post-rewrite URL.
To purge multiple URLs:
Select Multiple URLs, and enter the URLs you want to purge in the text box. You can enter up to 10 URLs at a time. You don't need to include the preceding protocol and ://; purges triggered from the portal do not distinguish between which protocol was used to request them when they were cached:
If you want to purge full directories (a prefix purge), use an asterisk (*); for example, ruraljuror.com/images/* will purge all cached objects that are from the /images directory.
Once you have specified the type of cache purge, click Purge Cache. You will see a confirmation message:
Click Yes, Purge Cache to proceed with the purge.
|Warning||Full domain and prefix purge operations can potentially purge a large number of objects from the cache, which can temporarily affect your site's performance.|
If you hover on the Tasks icon at the top of the screen will display a message like the following in the running tasks pane:
When the purge is completed, the running tasks pane will clear, the completed tasks pane should show that the cache purge was successful.
More control over cache purges (for example, performing wildcard purges, or submitting multiple requests at the same time) is available via the Cache Purge API; see the Cache Purge API Guide for details.