---
title: "Bypass Cache - New"
slug: "bypass-cache"
updated: 2025-01-26T16:23:25Z
published: 2025-01-26T16:23:25Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwilt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bypass Cache

## Overview

A Bypass Cache rule instructs the CDN to always fetch the content from the origin server.

For example, if your use case relies on real-time data or if you frequently update a particular content item and you want the latest version to be fetched from the origin server on every request, you can configure a Bypass Cache rule at the path level to ensure that the most up-to-date version of that content item is always served.

Note that when you set a Bypass Cache rule, previously cached content is not evicted from the cache.

## Configure the Rule

Here, we'll describe how to configure the rule with the Delivery Service Management UI.

API Users may choose to [build the site configuration offline](https://api-docs.qwilt.cqloud.com/docs/CDN%20APIs/Sites%20API/prepare-the-configuration-json).

**To configure a Bypass Cache rule:**

1. [Navigate to the Select Rule dialog](/v1/docs/add-a-rule).
2. In the Select Rule dialog, choose **Bypass Cache**.
3. Toggle on **Bypass Cache**. ![bypassCache2.png](https://cdn.document360.io/fa039225-513b-46a1-ba78-a57a1f1cb7c6/Images/Documentation/bypassCache2.png)
4. Choose **Add Rule**.

## SVTA Component: MI.CacheBypassPolicy

When you save the configuration version, the **MI.CacheBypassPolicy** component is added to the JSON configuration.

The Bypass Cache rule can be used to set client requests as non-cacheable.

In this example, the bypass-cache rule was added to the *.m3u8 path configuration so that requests for manifest files will always be fetched from the origin and not served from cache.

```
{
	"generic-metadata-type": "MI.CacheBypassPolicy",
	"generic-metadata-value": {
	"bypass-cache": true
	}
}
```