RunCache uses built-in and configurable rules to determine which requests can be served from cache and which should bypass caching. When a request bypasses the cache, RunCache reports X-RunCache-Status: BYPASS in the response header.
This guide explains how RunCache evaluates these rules, the order in which they apply, and what happens when a request matches more than one rule.
For details of the settings available under RunCache > Rules, see the Cache Rules documentation.
Why RunCache Bypasses Some Requests
Most WordPress pages display the same content to every visitor, making them suitable for caching. Some pages, though, contain content that changes depending on the visitor or the request and should not be cached.
Examples include shopping carts, checkout pages, logged-in areas, and page builder previews. RunCache bypasses caching for these requests so WordPress can generate the appropriate response rather than serving a previously cached version.
Built-In and Configurable Cache Rules
RunCache checks built-in exclusions before evaluating the configurable rules under RunCache > Rules.
These exclusions cover common requests involving WordPress administration, user logins, WooCommerce, and feeds. They cannot be disabled from the Rules screen.
| Rule type | Common built-in exclusions |
|---|---|
| URL paths | WordPress admin, login, feeds, XML-RPC, REST API, sitemap, cart, checkout, and account pages |
| Cookies | Logged-in sessions, password-protected content, comments, and WordPress settings cookies |
| Query strings | Feed requests |
Some built-in exclusions, such as WordPress administration and login paths, are not listed in the editable URL Path Exclusion field. They always apply, even though they cannot be viewed or changed from the Rules screen.

You can also create your own cache rules under RunCache > Rules. RunCache evaluates these alongside its built-in exclusions, following the evaluation order explained below.
For a full explanation of the available fields and settings, see the Cache Rules documentation.
Cache Rule Evaluation Order
RunCache checks each request against its cache rules in a fixed order, as shown below. If a request matches a rule that requires caching to be bypassed, RunCache stops evaluating subsequent rules for that request.
- Internal preload requests.
- HTTP method.
- Built-in query exclusions.
- Whether caching is enabled.
- The
DONOTCACHEPAGEconstant. - Built-in URL exclusions.
- Configurable URL, User-Agent, and visitor IP exclusions.
- Built-in cookie exclusions.
- Configurable cookie exclusions.
- Query-string rules.
The first matching bypass condition takes precedence, even if a later rule would otherwise allow caching.
For example, adding a query parameter to Include Cache Query String does not override an earlier exclusion based on the URL, cookies, User-Agent, or visitor IP address. Once RunCache identifies a matching bypass condition, it stops checking subsequent rules.
How Pattern Matching Works
RunCache uses wildcard matching rather than regular expressions when checking entries in the Rules fields. You can use the following characters to match different patterns:
*matches any sequence of characters.?matches a single character.%can also be used as an alternative to*.
RunCache does not interpret regular expression syntax such as [a-f0-9]+, .*, ^, or $ as a regular expression. Characters such as brackets, +, ^, and $ are treated literally, while * retains its wildcard meaning. Use the supported wildcard characters when creating matching patterns.
RunCache can also match entries without wildcards against part of a longer string. For example, an entry containing index.php can match a request for /blog/index.php.
Purge the Cache After Changing Rules
Changes to cache rules affect future requests, but they do not automatically remove pages cached under the previous settings.
After changing an exclusion or inclusion rule, purge the cache to remove any pages stored under the old rules. You can do this by clicking Purge Cache in the WordPress dashboard.
Alternatively, if you have access to WP-CLI, run the following command:
wp runcache purge