Non-Cached Paths
Overview
Non-Cached Paths exclude specific URL paths from edge caching. Requests
matching a listed path are never served from the edge cache and always
fetch fresh content from your server. Responses on these paths show
x-sucuri-cache: MISS.
Use this for URLs that return different content on every request: personalized pages, API endpoints, or routes that redirect to temporary signed URLs.
Adding a Non-Cached Path
From your WAF dashboard, navigate to Cache Rules > Non-cached Paths. Each entry has two fields:
| Field | Description |
|---|---|
| Match Type | How the path is compared to the request URL |
| Path | The URL path to exclude from caching |
Match types:
| Match Type | Matches |
|---|---|
| Begins with | Any URL whose path starts with the value |
| Ends with | Any URL whose path ends with the value |
| Equals | Only the exact path |
For example, a Begins With rule for /rails/active_storage/ excludes
every URL under that prefix.
Begins With and Equals paths start with /, because they match from the
start of the request path. If you leave the slash out or paste a full URL,
the dashboard saves just the path with a leading / and shows you what
was saved. The root path / on its own (for example, a pasted domain with
no path after it) can’t be added, since it would turn off caching for your
whole site.
Clear the Cache After Adding a Path
A new rule prevents future caching but does not remove responses that are already in the edge cache. Those continue to be served until they expire. After adding a path, click Clear Cache on the same page to remove any previously cached copies.
What Non-Cached Paths Do Not Change
Non-Cached Paths control edge caching only. They do not change the headers sent to visitors.
In particular, URLs that end in an asset file extension (images, CSS,
JavaScript, and similar) still receive far-future Cache-Control and
Expires headers from the edge network, even when the path is listed
here. Browsers will cache those responses locally regardless of the
cache MISS at the edge. See the Asset File Caching article for details
and workarounds.