> 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

Mobile Device Cache allows the CDN to generate different cache entries based on the detected device type. This ensures that each device category receives appropriately formatted content without cache conflicts.

The feature also forwards device information to your origin using the **X-DEVICE** and **X-MOBILE** headers.

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

Log in to the [Medianova Control Panel](https://cloud.medianova.com), select a CDN resource in the CDN section, and navigate to the **Caching** tab.

## Enable Mobile Device Cache

{% stepper %}
{% step %}
**Enable the Setting**

Switch **Mobile Device Cache** to **On** to create separate cached versions for mobile, tablet, and desktop.
{% endstep %}

{% step %}
**Submit the Configuration**

Click **Submit** to apply the updated caching behavior.
{% endstep %}
{% endstepper %}

## **Behaviour**

Mobile Device Cache changes how cache keys are generated and what information is forwarded to the origin.

#### **Device Classification**

The CDN classifies each request using the User-Agent header:

* **mobile**
* **tablet**
* **desktop**

#### **Cache Key Variation**

A unique cache entry is created per device type, for example:

```
/index.html | mobile
/index.html | desktop
```

#### **Forwarded Headers**

<table><thead><tr><th width="154">Header</th><th width="323.0001220703125">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>X-DEVICE</strong></td><td>Device category detected by the CDN</td><td><code>mobile</code> / <code>tablet</code> / <code>desktop</code></td></tr><tr><td><strong>X-MOBILE</strong></td><td>Whether the device is mobile</td><td><code>true</code> / <code>false</code></td></tr></tbody></table>

These headers allow your origin to serve tailored content if needed.

* Device detection is based on User-Agent parsing and may not be accurate for all custom or rare device signatures.
* The feature does not provide per-resolution caching (e.g., based on screen width).
* Use this feature only if your mobile/tablet/desktop content differs meaningfully.

## **FAQ**

#### **Does Mobile Device Cache change how requests are routed to the origin?**

No. This feature affects only cache segmentation and forwards device headers. Origin routing remains unchanged.

#### **What happens if the CDN cannot identify the device type from the User-Agent?**

The request is classified as **desktop** by default, and the cache key is generated accordingly.

#### **Will enabling this feature create separate cached versions for each device type?**

Yes. Mobile, tablet, and desktop clients each receive their own cached version, preventing cross-device content mismatches.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/mobile-device-cache.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.