Force Internal Max-Age

This feature determines the 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 can check whether a cached asset matches the asset stored on the origin server.

Key information:

• This action will override the max-age interval defined in Cache-Control or Expires headers generated from an origin server.
• 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.
• This feature does not have an observable effect on the response delivered by an edge server to the requester. However, it may have an effect on the amount of revalidation traffic sent from our edge servers to the origin server.
• Configure this feature by:
  • Selecting the status code for which an internal max-age will be applied.
  • Specifying an integer value and selecting the desired time unit (i.e., seconds, minutes, hours, etc.). This value defines the request's max-age interval.
• Setting the time unit to "Off" disables this feature. An internal max-age interval will not be assigned to requested assets. If the original header does not contain caching instructions, then the asset will be cached according to the active setting in the Default Internal Max-Age feature.

Default Behavior: Off

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.