Help Center/
Content Delivery Network/
FAQs/
Cache Purge and Prefetch/
Why Does a Cache Prefetch Operation Fail?
Updated on 2024-10-16 GMT+08:00
Why Does a Cache Prefetch Operation Fail?
The following lists the possible causes. You can view the detailed cause on the Task Progress tab of the Prefetch & Purge page on the CDN console.
- A large number of files are being prefetched at the same time, and this occupies all of the origin server's bandwidth. Perform prefetch in batches, or increase the bandwidth of the origin server to improve the efficiency.
- The cache TTL of your requested content is 0. Modify the cache setting.
- Cache-Control is set to private, no-cache, or no-store on the origin server and Origin Cache Control is enabled on the CDN console.
- You requested to prefetch directories or dynamic content.
- Your origin server cannot be accessed due to network errors, security restrictions such as firewalls and ACLs on the origin server, or other issues.
- Cross-border prefetch may exist, that is, the origin server location is not in the same area as the prefetch PoP. For example, the origin server is outside the Chinese mainland and the PoP is in the Chinese mainland.
Parent topic: Cache Purge and Prefetch
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot