Set this behavior to cache content on Akamai platform servers and associate caching instructions with content sent downstream to browsers or mobile devices.
How it works
Default settings apply to all objects under your property configuration. For example, the caching setting tells the edge servers to cache content for an infinite time and remove the least recently used objects (LRU) to make room for new ones and free capacity. Using this behavior, you can modify the default values or create more complex caching instructions.
Caching options
Cache
Select this option to cache content in Akamai platform servers for the time you specify in the Maxage field. Once cached, edge servers calculate the remaining time to live (TTL) in cache for the object. Setting a positive time, you can choose units of seconds, minutes, hours, or days.
If you set Maxage to 0, edge servers cache the content and revalidate it with the origin for every request – similar to how Cache-Control: no-cache works with browser caches.
In the Force revalidation of stale objects field, specify what to do when an object’s caching life has expired. Edge servers can either serve the object only if it has been re-fetched or validated at the origin or serve stale, which is useful when the origin is not available.
No store
Select this option to serve the content from the origin and clear any versions from the edge cache. Additionally, No store disables downstream caches, so you can configure edge servers to send these cache-busting headers downstream to the clients:
- Expires: <current_time>
- Cache-Control: max-age=0
- Cache-Control: no-store
- Pragma: no-cache
Bypass cache
Select this option to serve the content from the origin without removing any cached versions from edge servers. Bypass cache also disables downstream caches.
You might want to bypass the cache for the client requests when using central authorization. If the user authenticates, you can redirect them to the cached content. Otherwise, edge servers return a login module.
Honor origin Cache-Control and Expires
Select this option to configure content caching through honoring the Cache-Control and Expires response headers from the origin.
For Honor origin Cache-Control and Honor Cache-Control and Expires options, if the Cache-Control header contains the must-revalidate or proxy-revalidate directives, edge servers ignore the Force revalidation of stale objects setting and don’t serve stale content unless validated with the origin server. If the must-revalidate or proxy-revalidate directives are not present in the Cache-Control header, in the Force revalidation of stale objects field, specify what to do when an object’s caching life has expired. Edge servers can either serve the object only if it has been re-fetched or validated at the origin, or serve stale, which is useful when the origin is not available.
Set the Default maxage edge servers can use in case the relevant origin header is not found or is invalid. Default maxage is ignored if another honored directive that affects TTL is used by the origin.
You can enable Enhanced RFC support that lets you honor additional Cache-Control header directives from the origin. The directives adhere to RFC-standards, except for the no-transform one, which is disabled by default. The directives are grouped by functionality.