Help Center/
Content Delivery Network/
FAQs/
Cache Purge and Prefetch/
Why Do Users Still Access the Stale Resource After It Has Been Updated on the Origin Server and Its Cache on CDN Has Been Purged?
Updated on 2024-10-16 GMT+08:00
Why Do Users Still Access the Stale Resource After It Has Been Updated on the Origin Server and Its Cache on CDN Has Been Purged?
Possible causes:
- You have prefetched resources before purge and the operation interval may be too short. It is recommended that the interval be longer than 5 minutes.
- Resource update is not complete on the origin server before purge. As a result, CDN cannot pull the updated resource.
- The URL entered for purge is incorrect, or the directory does not contain the resource. Take domain name example.com and image /test/test1/1.jpg as an example.
- When you set the purge type to URL, the entered resource URL should be http://example.com/test/test1/1.jpg.
- When you set the purge type to Directory, the entered resource URL should be http://example.com/test/. If you enter http://example.com/test/test1/, CDN cannot pull the image.
- No parameter is contained during purge. If the resource URL contains parameters and you have set a cache rule for this resource to retain all or specific parameters, the parameters must be contained during purge.
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