Debug Cache Response Headers

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: Headers

Purpose: Determines whether a response may include debug cache response headers which provide information on the cache policy for the requested asset.

Our CDN returns debug cache response headers when both of the following are true:

The Debug Cache Response Headers feature has been enabled on the desired request.
The request defines the set of debug cache response headers that will be included in the response.

Request debug cache response headers by setting the X-EC-Debug request header to the desired debug cache response headers:

X-EC-Debug: Debug Cache Header 1,Debug Cache Header 2,Debug Cache Header N

Example:

X-EC-Debug: x-ec-cache,x-ec-check-cacheable,x-ec-cache-key,x-ec-cache-state

Enabled	Result
Yes	Requests that include the X-EC-Debug header return a response that includes the specified debug cache response headers.
No	The response always excludes debug cache response headers.

Default Behavior: Disabled.

More Information

Debug Cache Response Headers Information