> 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/range-based-caching.md).

# Range Based Caching

Cache partial content based on byte ranges so the CDN can serve only the requested portions of large files.

**Range Based Caching** partitions cacheable content into byte-range segments. This allows partial content requests to be served from cached segments instead of requiring the entire object to be fetched from the origin.

This behavior is useful for workloads that commonly use **206 Partial Content** responses, including video streaming, large file downloads, and binary file delivery.

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

## Configure Range Based Caching

{% stepper %}
{% step %}

### Open Range Based Caching

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

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2Fxtk7E3mQZba38Y6S528J%2Fimage.png?alt=media&amp;token=f67599d4-85c8-48d9-9bb8-e43ebed56463" alt=""><figcaption></figcaption></figure>

Locate the **Range Based Caching** section.
{% endstep %}

{% step %}

### Enable Range Based Caching

Enable **Range Based Caching**.

When enabled, the CDN can cache content in fixed-size byte-range segments and serve partial requests from those cached segments.
{% endstep %}

{% step %}

### Select the Segment Size

Select a value from **Segment Size**.

The Segment Size determines how the CDN partitions and stores cached byte ranges.

* Smaller segments provide greater cache precision for partial requests.
* Larger segments reduce the number of cache objects created for the content.

{% hint style="info" %}
Changing the **Segment Size** affects newly cached segments. Existing cached segments remain available until they are naturally evicted from the cache.
{% endhint %}
{% endstep %}

{% step %}

### Save the Configuration

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

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

## How Range Based Caching Works

When a client requests only part of an object, the request can use an HTTP byte range and receive a **206 Partial Content** response.

With Range Based Caching enabled, the CDN stores content in segments according to the configured **Segment Size**. Subsequent requests for cached portions can be served from the edge instead of repeatedly requesting those portions from the origin.

{% hint style="info" %}
Byte-range requests work independently of this setting. Range Based Caching determines whether partial content can be stored and reused from the CDN cache.
{% endhint %}

Range Based Caching is commonly applicable to content such as video files, large downloads, and other binary objects that clients access using partial content requests.


---

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