Help Center>
Content Delivery Network>
FAQs>
Cache Purge and Prefetch>
Why Does a Cache Prefetch Operation Fail?
Updated on 2024-04-17 GMT+08:00
Why Does a Cache Prefetch Operation Fail?
It is possible that:
- 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 maximum cache age 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 content cannot be accessed.
Parent topic: Cache Purge and Prefetch
Cache Purge and Prefetch FAQs
- What Are the Differences Between Cache Purge and Cache Prefetch?
- Why Am I Seeing Insufficient Permission for Cache Purge and Prefetch?
- Why Does a Cache Prefetch Operation Fail?
- Does Cache Purge Refresh Content Cached on All PoPs?
- Should I Enter an Origin URL or Domain Name URL for Cache Purge and Prefetch?
- Why Does a Prefetch Task Remain in the Being Processed Status for a Long Time?
- How Do I Purge the CDN Cache Where the Domain Name Includes a Wildcard?
- Why Is the Content Not Updated Even After I Prefetched and Purged the Cache?
- Does CDN Support Directory Prefetch?
- Are Cache Purge and Prefetch Mandatory?
- Do I Need to Purge or Prefetch the Cache of Both HTTP and HTTPS URLs?
- Can I Prefetch M3U8 Files?
- Which Should I Do First, Purge or Prefetch, When I Want to Update Cache?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more