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.

To configure a Bypass Cache rule:

1. Navigate to the Select Rule dialog.

2. In the Select Rule dialog, choose Bypass Cache.

3. Toggle on Bypass Cache.
   

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
	}
}