MNUID Cookie Base Cache
Learn how to configure MNUID Cookie Base Cache for Dynamic CDN Resources to create session-aware cached content.
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.
This feature is available only for Dynamic CDN Resources.
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.
Cached responses remain valid for the duration defined in Cookie Expiry Time.
After the expiry time elapses, the cached content is refreshed from the origin.
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 Medianova Control Panel.
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.
Enable MNUID Cookie Base Cache
Set Status to On.

Set the Cookie Expiry Time
Enter the Cookie Expiry Time in seconds.
This value defines how long cached content remains valid for requests that include the MNUID cookie.
Apply the Configuration
Select Submit to save and apply the changes.
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.
Setting a very short expiry time may reduce cache efficiency.
This feature affects cache key generation, not cache bypass.
Can be combined with Cookie Base Cache and Header Base Cache for advanced session-aware caching strategies.
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
Last updated
Was this helpful?