Cache purge is to clear resources cached on nodes. After purge, when a user accesses a resource, the latest resource will be obtained through origin-pull for response.
After cache purge, as there is no cache of the resource on nodes, the resource can be obtained only through origin-pull, and the number of origin-pull requests will increase for a short period, which will compromise the acceleration effect. If many cached resources are purged, a large number of origin-pull requests will be generated, bringing pressure on the origin server.
When a resource is updated on the business origin server, you need to purge the old resource cached on nodes to prevent users from getting the old resource. After the cache is purged in the entire network, users can get the latest resource.
If there are non-compliant resources at your business site, you need to clear them and rectify your site promptly. As such resources may still be cached on nodes, you need to purge them from nodes.
If a wildcard domain under the current site (example.com) such as
*.foo.example.comis connected, this option cannot take effect, and you need to submit the cache purge task for each subdomain separately.
You cannot submit URLs in the format of
http://*.test.com/; that is, domains cannot contain
*. You need to specify the corresponding subdomains.
Check whether the submitted content meets the following specifications:
- The encoding rules must comply with RFC 3986.
- Spaces must be encoded to
%20no matter where they are.
- If encoding conversion is involved, only resources matched after encoding conversion will be purged.
|Item||Maximum Quantity per Submission||Maximum Quantity per Day|
If you select file upload as the URL submission method, there is no limit on the number of URLs that can be submitted each time, but the number of submitted URLs will be deducted from the daily quota.