Configuring Auto Cache Refresh for the CDN Acceleration Domain Name of a Bucket
Scenarios
CDN acceleration caches data stored in OBS to edge PoPs, which enables faster access for users. When you need to update data stored in OBS, the data cached in CDN also needs to be updated. You can use the auto cache refresh function of CDN to update data. With this function enabled, the cached data on CDN nodes can be consistent with the data stored on the origin server (OBS).
Constraints
- Buckets that have versioning enabled or suspended do not support the auto cache refresh function of CDN.
- Folder cache cannot be automatically refreshed.
- Cross-tenant CDN cache cannot be automatically refreshed.
- The CDN cache of accounts with federated identity authentication cannot be automatically refreshed.
- If the CDN acceleration domain name is changed to a non-acceleration domain name (acceleration disabled) and the non-acceleration domain name triggers messages for more than 10 times within 5 minutes, auto cache refresh will be disabled automatically.
- If the CDN acceleration domain name is abnormal, auto cache refresh will be disabled automatically. You can configure auto cache refresh again after the domain name is restored.
- The Tenant Administrator permission is required for configuring auto cache refresh for the CDN acceleration domain name of a bucket. You are advised to use IAM for authorization. For details, see Using IAM to Grant Access to OBS.
Prerequisites
You have configured an acceleration domain name on OBS Console (meaning that acceleration has been enabled for the domain name).
Procedure
OBS allows you to configure auto CDN cache refresh for the acceleration domain name of a bucket on OBS Console. The procedure is as follows:
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot


