Default Internal Max-Age

This feature 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. These types of revalidations are 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:
  • Selecting the status code for which a default internal max-age can be applied.
  • Specifying 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.
• Setting the time unit to "Off" will assign a default internal max-age interval of 7 days for requests that have not been assigned a max-age indication in their Cache-Control or Expires header.

Default Value: 7 days

Note: Due to the manner in which cache settings are tracked, this feature cannot be associated with the following match options: Edge Cname, Request Header Literal, Request Header Wildcard, URL Query Literal, and URL Query Wildcard.