> 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/static-content-delivery/advanced-configuration/caching/mobile-device-cache.md).

# Mobile Device Cache

Define device-based caching behavior to create separate cached versions for mobile, tablet, and desktop clients.

**Mobile Device Cache** separates cached content based on the detected device type. When enabled, the CDN also provides device information to the origin through the **X-DEVICE** and **X-MOBILE** headers.

You can manage Mobile Device Cache in the [Medianova Control Panel](https://cloud.medianova.com).

## Configure Mobile Device Cache

{% stepper %}
{% step %}

### Open Mobile Device Cache

Open your CDN Resource and select **Caching**.

Locate the **Mobile Device Cache** section.
{% endstep %}

{% step %}

### Enable Mobile Device Cache

Enable **Mobile Device Cache**.

When enabled, the CDN separates cached content by device type and forwards the detected device information to the origin.
{% endstep %}

{% step %}

### Save the Configuration

Click **Save** in the pending changes bar.

Review the pending changes and confirm the update.
{% endstep %}
{% endstepper %}

## How Mobile Device Cache Works

When Mobile Device Cache is enabled, device information becomes part of the caching behavior so content intended for different device types can be stored separately.

The CDN also sends the following headers to the origin:

<table><thead><tr><th width="306">Header</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>X-DEVICE</strong></td><td>Provides the detected device type to the origin.</td></tr><tr><td><strong>X-MOBILE</strong></td><td>Provides mobile-device information to the origin.</td></tr></tbody></table>

This allows the origin to use the device information when generating a response.

{% hint style="info" %}
Enable Mobile Device Cache when your origin returns different content depending on the requesting device. Separating device-specific responses prevents those variants from sharing the same cache object.
{% endhint %}


---

# 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/static-content-delivery/advanced-configuration/caching/mobile-device-cache.md?ask=<question>&goal=<user_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.