> 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.md).

# Caching

Configure how Medianova CDN caches, validates, and delivers content for your CDN Resource.

Caching settings determine how responses are stored and reused at CDN edge servers. They provide control over cache expiration, request variations, content validation, error response caching, and delivery of cached content under specific conditions.

Caching settings are configured per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com/).

## Cache Configuration

The **Caching** section includes the following features:

* [**Edge Cache Expiration**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/edge-cache-expiration.md) – Configure how long content remains cached at CDN edge servers.
* [**Browser Cache Rule**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/browser-cache-rule.md) – Configure how long browsers cache delivered content.
* [**Query String Caching**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/query-string-caching.md) – Control how URL query strings affect cache behavior.
* [**ETag Verification**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/etag-verification.md) – Configure cache validation using HTTP ETag headers.
* [**Error Status Code Cache Expiration**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/error-status-code-cache-expiration.md) – Configure cache expiration for supported HTTP error responses, including 404 responses.
* [**Shared Cache**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/shared-cache.md) – Configure shared caching behavior for the CDN Resource.
* [**Stale Cache**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/stale-cache.md) – Configure the use of expired cached responses under supported conditions.
* [**Robots.txt File**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/robots.txt-file.md) – Configure how the CDN handles `robots.txt` requests.
* [**Range Based Caching**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/range-based-caching.md) – Configure segmented caching and delivery for supported HTTP Range requests, particularly for large objects such as videos and PDF files.
* [**Mobile Device Cache**](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/caching/mobile-device-cache.md) – Configure cache behavior for requests from mobile devices.

## Important Notes

Caching settings can influence content freshness, cache efficiency, and requests to the origin server. Select the appropriate configuration based on your application's content characteristics and delivery requirements.


---

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