> 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/mobile-device-cache.md).

# Mobile Device Cache

Learn how Mobile Device Cache enables device-based caching for dynamic content delivery.

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** [**Mobile Device Cache documentation**](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/mobile-device-cache.md)**.**


---

# 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/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.