Force 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 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 feature will override the max-age interval defined in Cache-Control or Expires headers generated from an origin server.
This feature 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:
1. Select the status code for which this 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 internal max-age interval that will be applied.
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 Behavior: Disabled. 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.