Disallow Cookie Base Cache

Control CDN caching behavior by excluding requests that contain specific cookie values.

The Disallow Cookie-Based Cache feature allows you to bypass CDN caching for requests that include defined cookie key–value pairs. This ensures that personalized or session-based content is always fetched from the origin instead of being served from cache.

Use this feature to prevent incorrect caching of dynamic responses while maintaining optimal cache efficiency for all other traffic.

This helps you avoid caching personalized or session-based responses on Dynamic Content Acceleration resources.

How Disallow Cookie-Based Cache Works

When the feature is enabled:

• The CDN inspects incoming requests for the configured cookie key–value pairs.

• If any defined pair matches, the request bypasses the cache.

• The response is fetched directly from the origin and is not stored in the CDN cache.

• Requests that do not match any configured cookie rules continue to follow normal caching logic.

This behavior applies consistently across all requests for the selected CDN Resource.

Configure Disallow Cookie-Based Cache

You can configure this feature from the Medianova Control Panel.

1

Enable the Feature

In the Caching tab of your Dynamic CDN Resource, set Disallow Cookie-Based Cache to On.

The cookie rule inputs become available.

2

Define Cookie Rules

Enter the cookie details:

• Cookie Key — Name of the cookie to match

• Cookie Value — Value that triggers cache bypass

Select + to add additional cookie rules if required.

3

Save changes

Select Submit to save and apply the changes.

• Cache bypass is triggered if any defined cookie rule matches.

• Cookie matching is exact; both key and value must match.

• This feature affects cache eligibility only and does not modify headers or routing logic.

• Requests that do not include matching cookies continue to benefit from CDN caching.

• Use carefully together with Page Rules to avoid unintended cache bypass.

Troubleshooting

Issue: Responses are still cached. Cause: The incoming cookie value does not exactly match the configured key-value pair. Fix: Capture the request cookies from the client and confirm the exact key and value.

Issue: Cache hit ratio drops unexpectedly. Cause: Too many cookie pairs are configured, or a widely present cookie is included. Fix: Remove non-essential cookies and keep only cookies that must bypass cache.

Issue: Configuration does not take effect. Cause: Changes were not saved. Fix: Confirm you selected Submit and re-check the setting state in the Caching tab.