> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/caching/mnuid-cookie-base-cache.md).
# 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.
{% hint style="info" %}
This feature is available **only for Dynamic CDN Resources**.
{% endhint %}
## 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](https://cloud.medianova.com).
{% stepper %}
{% step %}
**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.
{% endstep %}
{% step %}
**Enable MNUID Cookie Base Cache**
Set **Status** to **On**.
{% endstep %}
{% step %}
**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.
{% endstep %}
{% step %}
**Apply the Configuration**
Select **Submit** to save and apply the changes.
{% endstep %}
{% endstepper %}
* 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
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/caching/mnuid-cookie-base-cache.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
