> 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/browser-cache-rule.md).
# Browser Cache Rule
Configure browser-side caching behavior for different resource types using Browser Cache Rules.
**Browser Cache Rule** controls browser-side caching through response cache headers. Rules can target all files or specific paths, directories, and file extensions.
You can manage Browser Cache Rules 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-1).
{% hint style="info" %}
Browser Cache Rules control caching in end-user browsers and do not change CDN edge caching behavior. To configure caching on CDN edge servers, use Edge Cache Expiration.
{% endhint %}
## Cache Modes
Each Browser Cache Rule uses one of the following cache modes:
Cache Mode
Behavior
Origin
Honors the caching headers provided by the origin server.
No Cache
Disables browser caching and forces fresh requests.
Cache
Overrides origin caching headers and applies a configured cache duration.
## Configure a Browser Cache Rule
{% stepper %}
{% step %}
### Open Browser Cache Rule
Open your CDN Resource and select **Caching**.
Under **Browser Cache Rule**, select **Add rule**.
{% endstep %}
{% step %}
### Select the Rule Type
Select how the rule matches content:
* **All Files** – Applies the rule to all files.
* **Full Path** – Matches a specific full path.
* **Directory** – Matches content under a specified directory.
* **File Extension** – Matches files by extension.
Additional matching fields are displayed when required by the selected type.
{% endstep %}
{% step %}
### Set the Priority
Set the **Priority** value for the rule.
Rules are evaluated by priority, with lower numeric values taking precedence. If a request matches multiple rules, the matching rule with the higher precedence is applied.
{% endstep %}
{% step %}
### Select the Cache Mode
Select how browser caching is handled:
* **Origin** – Use caching headers provided by the origin.
* **No Cache** – Disable browser caching.
* **Cache** – Override origin caching headers and configure browser caching for a defined duration.
Configure any additional fields displayed for the selected mode.
{% endstep %}
{% step %}
### Add the Rule
Select **Add rule**.
The rule is added to the Browser Cache Rule list.
{% endstep %}
{% step %}
### Configure HTML/JSON Behavior
Use **Apply the HTML/JSON files** to control whether Browser Cache Rules also apply to HTML and JSON content.
{% 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 %}
## Rule Evaluation
Browser Cache Rules are matched according to their configured type and priority.
The rule list displays the configured:
* **Type**
* **Content**
* **Priority**
* **Cache Mode**
* **Cache Time**
* **Directive**
* **Exact Match**
Lower numeric priority values take precedence when multiple rules can match the same request.
{% hint style="info" %}
Use longer browser cache durations for static assets that change infrequently and shorter durations for frequently updated content.
CDN purge operations clear cached content from CDN edge servers but do not remove content that has already been stored in an end-user's browser.
{% 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/browser-cache-rule.md?ask=&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.
