Automatic Cache Invalidation
Automatic cache invalidation keeps cached content accurate by not serving outdated data. It also means you don't have to make manual updates every time you update the hosted files.
For files stored under File Cabinet > Web Site Hosting Files, automatic cache invalidation is only triggered in the following scenarios
-
When you modify the content of a hosted file
-
When you overwrite a hosted file or media item
For hosted files, automatic cache invalidation is not triggered in the following scenarios:
-
When you move, delete, or rename an existing hosted file or media item
-
When you upload a new file
If automatic cache invalidation isn't triggered, you can manually invalidate the cache as described in Cache Invalidation Request. However, in most cases, you don't need to because if the URL changes or is new, there's no cache to clear.
You can see the status of the triggered cache invalidation requests on the Cache Invalidation Status page. On this page, you can also filter to show only automatically triggered requests by selecting Automatic in the Request Type field. For more information, see Cache Invalidation Status.
Frequently changed files aren't cached on CDN to improve processing performance.
Group Cache Invalidation
To cut down on individual cache invalidation requests, group invalidation requests are created in the following situations:
-
When you use SOAP web services to upload files to the File Cabinet.
-
When you upload a
.zipfile to the File Cabinet as described in Uploading Files to the File Cabinet.
If a certain threshold is reached, multiple path invalidation requests might be replaced with a single wildcard invalidation request.
Cache invalidation requests in a group share the same timestamp, which you can see on the Cache Invalidation Status page.
To improve processing performance, automatic throttling is enabled for automatic cache invalidation. This makes sure that your environment doesn't generate too many cache invalidation requests. For example, scheduled scripts that modify files in your environment might generate a lot of cache invalidation requests, which then triggers automatic throttling.
In these cases, a cache invalidation request is created, but automatic throttling disables it. Consequently, you'll see the status as Suspended on the Cache Invalidation Status page.