edit-icon download-icon

How to Refresh Cached Files if They Are Inconsistent with Source Files?

Last Updated: Jan 29, 2018

After using the CDN product, you may want to update the origin site and publish it through the old URL. You need synchronously refresh the CDN node cache after origin site updates to ensure the content of origin site is consistent with that of the CDN cache. Currently, two refresh methods are available on the [Refresh] page in the CDN Console:

1

URL refresh

Set certain files on the CDN CACHE node as expired so back-to-source update will be performed on them. It will take effect five to ten minutes. Each ID can refresh up to 2,000 URLs each day.

Note: The URL entered must contain http://

Directory refresh

Set files of a directory on the CDN CACHE node as expired so back-to-source update will be performed on them. This method is suitable for scenarios with large amounts of content. It will take effect within 30 minutes. You can submit up to 100 refresh requests each day.

Note: The content entered must begin with http://, and end with /. Additionally, directory refresh must be performed in the directory refresh tab; otherwise, URL refresh will only refresh the singe URL rather than the all the files under the directory.

Thank you! We've received your feedback.