> 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/edge-cache-expiration.md).

# Edge Cache Expiration

Configure edge cache TTL and choose whether cache duration is controlled by the CDN, origin headers, or dynamic cache bypass.

**Edge Cache Expiration** controls the time-to-live (TTL) of cached content on CDN edge servers. Depending on the selected **Cache Type**, the CDN can use a fixed TTL, follow cache headers from the origin, or bypass edge caching.

You can manage Edge Cache Expiration in the [Medianova Control Panel](https://cloud.medianova.com) or via the [API](https://clients.medianova.com/api-documentation/performance-cdn/caching#put-api-v1-cdn-organization_uuid-resource-resource_uuid).

{% hint style="info" %}
Edge Cache Expiration controls caching on CDN edge servers. To configure client-side browser caching, see Browser Cache Rule.
{% endhint %}

## Cache Types

Edge Cache Expiration provides three cache types:

<table><thead><tr><th width="134.4000244140625">Cache Type</th><th>Behavior</th></tr></thead><tbody><tr><td><strong>Edge</strong></td><td>Uses the TTL configured in the Control Panel and overrides cache headers from the origin. A Cache Time value of <code>0</code> disables edge caching.</td></tr><tr><td><strong>Origin</strong></td><td>Uses the <code>Cache-Control</code> or <code>Expires</code> headers returned by the origin. If the origin does not provide a cache duration, the configured Cache Time is used as a fallback. A Cache Time value of <code>0</code> disables caching.</td></tr><tr><td><strong>Dynamic</strong></td><td>Bypasses edge caching. Requests are forwarded to the origin without being cached on CDN edge servers.</td></tr></tbody></table>

When **Dynamic** is selected, **Cache Time** is not configurable.

## Configure Edge Cache Expiration

{% stepper %}
{% step %}

### Open Caching

Open your CDN Resource and select **Caching**.
{% endstep %}

{% step %}

### Select the Cache Type

Under **Edge Cache Expiration**, select one of the following from **Cache Type**:

* **Edge**
* **Origin**
* **Dynamic**
  {% endstep %}

{% step %}

### Configure Cache Time

For **Edge** or **Origin**, enter the **Cache Time** and select the corresponding time unit.

**Edge** uses this value as the TTL applied on CDN edge servers.

**Origin** uses this value as a fallback when the origin does not provide a cache duration through `Cache-Control` or `Expires`.

{% hint style="warning" %}
A Cache Time value of `0` disables caching when **Edge** or **Origin** is selected.
{% endhint %}

This step does not apply to **Dynamic**, because Dynamic bypasses edge caching.
{% endstep %}

{% step %}

### Save the Configuration

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

Review the pending changes and confirm the update to apply the configuration to the CDN Resource.
{% endstep %}
{% endstepper %}

## Cache Behavior

With **Edge**, the configured Cache Time determines how long cached content remains valid on CDN edge servers, regardless of cache expiration headers returned by the origin.

With **Origin**, the CDN first uses the cache duration provided by the origin through `Cache-Control` or `Expires`. The configured Cache Time is used when the origin does not provide a cache duration.

With **Dynamic**, edge caching is bypassed and requests are forwarded to the origin.

{% hint style="info" %}
Longer TTL values are generally suitable for static content that changes infrequently. Use shorter TTL values for content that is updated more frequently.
{% 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/edge-cache-expiration.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.