Property Manager Name: Caching
Control content caching on edge servers: whether or not to cache, whether to honor the origin’s caching headers, and for how long to cache. Note that any NO_STORE or BYPASS_CACHE HTTP headers set on the origin’s content overrides this behavior.
Options
- behavior (enum string): Specify the caching option:
- NO_STORE clears the cache and serves from the origin.
- BYPASS_CACHE retains the cache but serves from the origin.
- Honor the origin’s MAX_AGE header
- Honor the origin’s CACHE_CONTROL header
- Honor the origin’s EXPIRES header
- Honor CACHE_CONTROL_AND_EXPIRES the origin’s CACHE_CONTROL or EXPIRES header, whichever comes last.
Note. New CACHE_CONTROL_BETA and CACHE_CONTROL_AND_EXPIRES_BETA values add support for the s-maxage response directive specified in RFC 7234. Use these alternative values to instruct a downstream CDN how long
to cache content.
- mustRevalidate (boolean): Determines what to do once the cached content has expired, by which time the Akamai platform should have re-fetched and validated content from the origin. If enabled, only allows the re-fetched content to be served. If disabled, may serve stale content if the origin is unavailable.
- ttl (duration string): The maximum time content may remain cached. Setting the value to 0 is the same as setting a no-cache header, which forces content to revalidate.
- defaultTtl (duration string): Set the MAX_AGE header for the cached content.
- enhancedRfcSupport (boolean): With behavior set to either CACHE_CONTROL or CACHE_CONTROL_AND_EXPIRES, this enables honoring particular Cache-Control header directives from the origin. Supports all official RFC 7234 directives except for no-transform.
- honorNoStore (boolean): With enhancedRfcSupport enabled, this instructs edge servers not to cache the response when the origin response includes the no-store directive.
- honorPrivate (boolean): With behavior set to either CACHE_CONTROL or CACHE_CONTROL_AND_EXPIRES, enabling this instructs edge servers not to cache the response when the origin response includes the private directive.
- honorNoCache (boolean): With enhancedRfcSupport enabled and the no-cache directive present in the response, this instructs edge servers to validate or refetch the response for each request. Effectively, set the time to live ttl to zero seconds.
- honorMaxAge (boolean): With enhancedRfcSupport enabled, this instructs edge servers to cache the object for a length of time set by the max-age directive in the response. When present in the origin response, this directive takes precedence over the max-age directive and the defaultTtl setting.
- honorSMaxage (boolean): With enhancedRfcSupport enabled, this instructs edge servers to cache the object for a length of time set by the s-maxage directive in the response. When present in the origin response, this directive takes precedence over the max-age directive and the defaultTtl setting.
- honorMustRevalidate (boolean): With behavior set to either CACHE_CONTROL or CACHE_CONTROL_AND_EXPIRES, enabling this instructs edge servers to successfully revalidate with the origin server before using stale objects in the cache to satisfy new requests.
- honorProxyRevalidate (boolean): With enhancedRfcSupport enabled and the proxy-revalidate directive present in the response, this instructs edge servers to successfully revalidate with the origin server before using stale objects in the cache to satisfy new requests.