Show search and navigation.

 

Stale Content Delivery on Error

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. - Advanced

This capability requires Rules Engine - Advanced Rules which must be purchased separately. Contact your CDN account manager to activate it.

Category: Caching

Purpose: Determines whether expired cached content will be delivered when an error occurs during either cache revalidation or when retrieving the requested content from a customer origin server.

Enabled Result

Yes

Stale content will be served to the requester when an error occurs during a connection to an origin server.

Use the Internal Max-Stale feature to configure the length of time after TTL expiration during which stale content may be delivered.

Each stale response includes a Warning response header.

No

The origin server's error will be forwarded to the requester.

Default Behavior: Disabled