Header Base Cache

Control CDN caching behavior by varying cache entries based on specific HTTP request headers.

The Header Base Cache feature allows you to include selected HTTP request headers in the CDN cache key for Dynamic Content Acceleration resources.

This enables the CDN to create separate cached objects for different header combinations, ensuring correct delivery of dynamic or personalized content without disabling caching.

This feature is available only for Dynamic CDN Resources.

How Header Base Cache Works

When Header Base Cache is enabled:

• The CDN inspects incoming requests for the configured HTTP header keys.

• The specified headers and their values are included in the cache key.

• Requests with different header values are cached as separate variants.

• Requests that do not include the configured headers follow the default cache behavior.

This approach allows safe caching of responses that vary based on request headers such as language, device hints, or custom application headers.

Configure Header Base Cache

You can configure this feature from the Medianova Control Panel.

1

Open the Caching Settings

Log in to the Medianova Control Panel, navigate to CDN → CDN Resources, select a Dynamic CDN Resource, and open the Caching tab.

2

Enable Header Base Cache

Set Status to On.

The header input field becomes active.

3

Add Request Headers

Enter the header information:

• Header Key — Name of the HTTP request header to include in the cache key

Select the + button to add additional header keys if required.

4

Apply the Configuration

Select Submit to save and apply the changes.

• Each unique header value creates a separate cache entry.

• Header matching is based on the header name; values are evaluated dynamically.

• This feature affects cache key generation, not cache bypass behavior.

• Adding too many headers may increase cache fragmentation and reduce cache efficiency.

• Header Base Cache can be combined with Cookie Base Cache and Disallow Cookie Base Cache for advanced cache control strategies.

Common Use Cases

• Cache responses per language using Accept-Language

• Separate cache entries for feature flags or tenant identifiers

• Cache dynamic HTML or JSON responses that vary by request metadata

• Support multi-tenant or region-aware applications