The Edge Cache Expiration feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It defines how the CDN caches objects at the edge and how long cached responses remain valid before refreshing from the origin. You can configure cache modes that rely on Panel-defined TTL values, defer to origin headers, or disable caching entirely for dynamic workloads.

For configuration details, cache modes, and examples, refer to the main documentation: Learn more in the.

The Query String Caching feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It determines how the CDN evaluates query parameters when generating cache keys, allowing you to cache each query string variant separately, ignore specific parameters, or build cache keys using only selected values. These configurations provide granular control over caching behavior for dynamic endpoints, APIs, and personalized content.

For configuration details, caching modes, and examples, refer to the main documentation: Learn more in the .

The Error Status Code Cache Expiration feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It allows you to define custom cache durations for specific HTTP error codes so the CDN can temporarily store repeated error responses, reducing unnecessary load on the origin. Each status code can have its own TTL, and caching can be enabled or disabled per code based on your requirements.

For configuration details, supported behaviors, and examples, refer to the main documentation: Learn more in the .

The Browser Cache Rule feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It controls browser-side caching by defining cache duration, cache modes, and rule priorities for different URL patterns, directories, or file types. These rules determine how browsers store and revalidate dynamic content, independent of CDN edge caching behavior.

For configuration details, rule types, and examples, refer to the main documentation: Learn more in the .

The ETag Verification feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It compares the ETag value returned by the origin with the ETag of the cached object and refreshes the cache when a mismatch occurs. This ensures the CDN serves the most up-to-date version of dynamic content and prevents stale objects from being delivered to end users.

For configuration details, validation behavior, and examples, refer to the main documentation: Learn more in the.

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.

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.

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 .

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

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

The Stale Cache feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It allows CDN edge servers to deliver the last cached version of an object when the origin fails to respond or returns specific error codes. You can define which origin conditions—such as timeouts, invalid headers, or 5xx errors—trigger stale delivery. This improves availability for dynamic workloads during short-term origin instability.

For configuration details, supported triggers, and examples, refer to the main documentation: Learn more in the .

MNUID Cookie Base Cache generates separate cached versions of content based on the MNUID cookie value for Dynamic Content Acceleration resources.

This feature enables session-aware caching while maintaining control over cache lifetime through configurable expiry settings.

How MNUID Cookie Base Cache Works

When MNUID Cookie Base Cache is enabled:

• Medianova CDN checks incoming requests for the MNUID cookie.

• The value of the MNUID cookie is included in the cache key.

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

This mechanism allows session-aware caching while maintaining control over cache lifetime.

Configure MNUID Cookie Base Cache

You can manage MNUID Cookie Base Cache using the .

• Each unique MNUID value creates a separate cache entry.

• Cache variation is based on the cookie value, not just its presence.

• Cookie Expiry Time controls cache validity independently of origin headers.

Common Use Cases

• Cache dynamic pages per authenticated user session

• Improve performance for logged-in users while maintaining correctness

• Control cache lifetime for session-based personalization

• Reduce origin load for frequently accessed user-specific content

The Cookie Base Cache feature allows you to include selected cookies in the CDN cache key for Dynamic Content Acceleration resources. This ensures that different user sessions or states receive the correct cached response without disabling caching entirely.

How Cookie Base Cache Works

When Cookie Base Cache is enabled:

• The CDN inspects incoming requests for the configured Cookie Key values.

• The specified cookies are included as part of the cache key.

• Requests with different cookie values are cached separately.

This allows dynamic and personalized content to be cached safely without serving incorrect responses across users.

Configure Cookie Base Cache

You can configure this feature from the .

• Each unique cookie value creates a separate cache entry.

• Cookie matching is based on the cookie name only; values are evaluated dynamically.

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

Common Use Cases

• Cache dynamic pages per user role or session type

• Serve different cached responses for logged-in vs logged-out users

• Safely cache HTML or JSON responses that depend on cookie state

The Mobile Device Cache feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It allows CDN edge servers to create separate cache entries based on the client’s device type, ensuring that mobile, tablet, and desktop users receive the correct version of dynamic content without cache conflicts.

When enabled, the CDN also forwards device metadata to the origin using the X-DEVICE and X-MOBILE request headers. This enables device-aware logic at the origin while preserving cache integrity at the edge.

Cache behavior, device classification logic, and forwarded headers remain consistent across Static Content Delivery and Dynamic Content Acceleration.

For configuration steps, device categories, forwarded headers, and usage examples, refer to the main documentation: Learn more in the .

The Header Value Base Cache feature allows you to explicitly allow or deny caching when a request contains a specific HTTP header value. This provides precise control over caching behavior for Dynamic Content Acceleration resources where certain header values determine whether content should be cached.

The Shared Cache feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It determines whether CDN edge nodes use an isolated cache namespace for your account (Default) or a shared cache namespace across multiple accounts that use the same Domain Cache Key (Share). When shared mode is enabled, identical content is cached once and reused across participating accounts, improving efficiency and reducing redundant origin requests.

For configuration details, cache modes, and examples, refer to the main documentation: Learn more in the .

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.

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.

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

Configure Disallow Cookie-Based Cache

You can configure this feature from the .

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

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.