Configures cache lifetime for objects stored in the Fastly cache, overriding cache freshness information that would otherwise be determined from cache-related headers on the HTTP response. When used in conjunction with conditions, cache settings objects provide detailed control over how long content persists in the cache.
|String||If set, will cause vcl_fetch to terminate after processing this rule with the return state specified. If not set, other configuration logic in vcl_fetch with a lower priority will run after this rule.|
|Do not cache the response and do not apply request collapsing to subsquent requests for the period specified in the TTL.|
|Proceed to save the object and deliver the response.|
|Discard the response and restart VCL processing in vcl_recv.|
|String||Name of a condition object that should be used to test whether to apply the cache settings object.|
|String||Name for the cache settings object.|
|Integer||Maximum time in seconds to continue to use a stale version of the object if future requests to your backend server fail (also known as 'stale if error').|
|Integer||Maximum time to consider the object fresh in the cache (the cache 'time to live').|
User contributed notes
We welcome comments that add use cases, ideas, tips, and caveats. All comments will be moderated before publication. To post support questions, visit our support center and we'll find you the help you need.