Forcible Cache
Description
Forcible Cache determines whether to ignore the no-cache, private, and no-store directives in the Cache-Control response header of the origin server. When it is enabled, these directives are ignored.
Working with TTL Source
Forcible cache works with the time to live (TTL) source based on these rules:
- When TTL Source is set to Origin server and Forcible Cache is disabled:
- If no-cache, private, or no-store is set in the Cache-Control origin response header, CDN points of presence (PoPs) do not cache content.
- If other cache directives are set on the origin server, the priority is s-maxage > max-age > expires. For example, if Cache-Control: max-age=500, s-maxage=400 is set on the origin server, CDN caches content for 400s.
- If the preceding cache directives are not set, CDN uses the cache TTL set on its console.
- When TTL Source is set to Origin server and Forcible Cache is enabled:
- If cache directives are set on the origin server, the priority is s-maxage > max-age > expires. For example, if Cache-Control: max-age=500, s-maxage=400 is set on the origin server, CDN caches content for 400s.
- If the preceding cache directives are not set, CDN uses the cache TTL set on its console.
- When TTL Source is set to CDN and Forcible Cache is enabled:
- CDN ignores response headers from the origin server and uses the cache TTL set on the CDN console.
- When TTL Source is set to CDN and Forcible Cache is disabled:
- If no-cache, private, or no-store is set in the Cache-Control origin response header, CDN PoPs do not cache content.
- If no-cache, private, or no-store is not set on the origin server, CDN uses the cache TTL set on its console.
- When TTL Source is set to Whichever is shorter and Forcible Cache is disabled:
- When TTL Source is set to Whichever is shorter and Forcible Cache is enabled:
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.