Default Internal Max-Age

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Basic

Category: Caching

Purpose: Determines the default max-age interval for edge server to origin server cache revalidation. In other words, the amount of time that will pass before an edge server will check whether a cached asset matches the asset stored on the origin server.

Key information:

This action will only take place for responses from an origin server that did not assign a max-age indication in the Cache-Control or Expires header.
This action will not take place for assets that are not deemed cacheable.
This action does not affect browser to edge server cache revalidations.

Browser to edge server revalidation is determined by the Cache-Control or Expires headers sent to the browser, which can be customized with the External Max-Age feature.
The results of this action do not have an observable effect on the response headers and the content returned from edge servers for your content, but it may have an effect on the amount of revalidation traffic sent from edge servers to your origin server.
Configure this feature by performing the following steps:
1. Select the status code for which this default internal max-age policy will be applied.
  
  This feature is only applicable when the response to the request results in the selected status code.
2. Specify an integer value and then selecting the desired time unit (i.e., seconds, minutes, hours, etc.). This value defines the default internal max-age interval.
Due to the manner in which cache settings are tracked, this feature cannot be associated with the following match conditions:
- AS Number
- Client IP Address
- Cookie Parameter Literal
- Cookie Parameter Regex
- Cookie Parameter Wildcard
- Country
- Device
- Edge CNAME
- Referring Domain Literal
- Referring Domain Wildcard
- Request Header Literal
- Request Header Regex
- Request Header Wildcard
- Request Method
- Request Scheme
- URL Query Literal
- URL Query Regex
- URL Query Wildcard
- URL Query Parameter Literal
- URL Query Parameter Wildcard

Default Value: Requests that do not provide a max-age indication via either their Cache-Control or Expires header will be assigned a default internal max-age interval of 7 days.