Cache Settings

Cache Settings

Cache Settings allow you to control how your store uses Redis Full Page Caching. These settings determine how URL parameters, cookies, and headers affect the cached versions of your pages.

Caching helps your store load faster by saving previously generated pages so they can be served quickly without rebuilding them each time a visitor requests them.

In this guide

• How Caching Works

• Cache Keys

• Cache Rules

• Wildcard Parameter Support

Accessing Cache Settings

Access Cache Settings in the admin by navigating to: 

Path: Settings → Store Settings → Cache Settings tab

How Caching Works

When a visitor requests a page:

1. Miva checks if a cached version of the page already exists.

2. If a cached version is found, it is returned immediately.

3. If no cached version exists, the page is generated normally and then stored in the cache for future requests.

This process reduces server load and improves page speed.

Cache Keys

Each cached page is identified by a cache key, which is a unique identifier generated from the page request.

A cache key typically includes:

• The page URL (domain and path)

• Request parameters (GET or POST variables, such as URL query strings or form submissions)

• Selected cookies or headers

By default, all request parameters are included in the cache key. This means that different parameter values will generate different cache keys, resulting in multiple cached versions of the same page.

For example:

• /product.html?utm_source=google

• /product.html?utm_source=facebook

These would normally create separate cache entries, even though the page content is the same.

Cache Settings allow you to control how cookies, parameters, and headers affect caching behavior, including whether they are included in the cache key, ignored, or used to prevent a page from being cached.

Cache Rules

Each rule in the Cache Settings table includes the following fields:

Name - The name of the Cookie, Parameter, or Header the rule applies to.

Type – Determines where the value comes from in the request:

• Cookie –Data stored in the visitor’s browser (such as session or tracking data)

• Parameter – Values passed in the page URL (such as query string parameters)

• Header – Information sent in the HTTP request headers by the browser or server

Mode – Defines how the value affects caching behavior. In the UI dropdown, the following options are available:

• Include in Cache Key – The value is included in the cache key, creating separate cached versions for different values

• Don’t Include in Cache Key – The value is ignored and does not affect cached versions

• Don’t Cache Page if Present – The page will not be cached if the item exists in the request

• Don’t Cache if Item Contains Value – The page will not be cached if the value contains the specified text

• Don’t Cache if Item is Equal to Value – The page will not be cached if the value exactly matches the specified value

Wildcard Parameter Support (10.13.04+)

The Name field in Cache Rules supports wildcard matching for Parameter types. A trailing asterisk (*) can be used to match multiple parameters that share the same prefix.

Example: utm_*

This rule will match any parameter beginning with utm_, including:

• utm_source

• utm_campaign

• utm_medium

• utm_term

• utm_content

For example, the following URLs may contain tracking parameters:

/product.html?utm_source=google
/category.html?utm_campaign=spring-sale
/index.html?utm_medium=email

In a URL parameter, the text before the = is the parameter name and the text after it is the value. For example, in utm_source=google, the parameter name is utm_source and the value is google , indicating that the visitor came from Google.

Using a wildcard allows a single rule to apply to groups of related parameters instead of adding each parameter individually. Without this rule, each parameter variation could create a separate cache key for the same page.

Learn More

For full details on configuring Redis caching, including cache keys, page-level settings, and advanced configuration, see: Redis Full Page Caching Documentation