Overview
CDN caches origin content on PoPs across the globe so that users can obtain content from nearby PoPs. You can modify rules and relevant settings of caches on CDN PoPs.
- You can modify cache settings of a domain name that is in the Enabled or Configuring state and is not locked or banned.
Function |
Description |
---|---|
|
|
You can set a browser cache TTL, during which users can obtain content directly from their browser cache (if available), reducing origin pulls. |
|
You can cache error codes returned by the origin server to CDN PoPs in a specific duration, so that CDN returns the error codes to users when they request content. This can reduce origin pulls and relieve the pressure on the origin server. |
|
You can set access URL rewrite rules to redirect user requests to the URLs of cached content. |
|
If different domain names point to the same resources, you can configure a shared cache group and set a primary domain name. Other domain names in the group share the cache of the primary domain name, improving the cache hit ratio. |
- If you have modified the cache rules and origin cache control settings,
- Your modifications are effective for new content cached.
- You can purge to apply modifications to the existing cache.
Feedback
Was this page helpful?
Provide feedbackThank 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