Purge via the dashboard

Quant clears caches automatically when content changes. The dashboard purge tool is for the cases where you want to trigger a purge manually — for example if content appears “stuck”, or you want to clear caches outside of a deployment.

Where to find it

From your project in the dashboard, open Purge Cache. You need the edit_projects permission on the project.

Purge by URL

Enter a URL path — no domain, just the path starting with a slash.

• A specific path, e.g. /blog/my-post, purges that page.
• /* purges the entire cache for the project.
• A prefix wildcard such as /images/* works on QuantGov, and on QuantCDN projects whose Purge Cache page says “Wildcards are supported”. On other QuantCDN projects, /* is the only wildcard and any other path is purged exactly; use cache keys for groups of pages.

Purge by cache key

Instead of a URL, you can purge by one or more cache keys, separated by spaces (e.g. env:test release:1.4.2). Every cached object tagged with any of those keys is purged.

This requires your origin to emit a Cache-Keys response header on the content you want to tag — see Using cache keys for the full explanation.

The URL and cache-key fields are mutually exclusive: filling one disables the other.

Note

There is no dashboard view that lists the cache keys in use for a project. Keys are a convention you define and track on your side.

Soft purge

The Soft purge toggle marks content as stale rather than deleting it immediately, allowing stale content to still be served if your origin is unavailable. The toggle is on by default. It is shown on QuantCDN projects; QuantGov has no soft purge, and every purge removes the content.

See also

• Using cache keys — how to tag content for key-based purging.
• Purge via the API — the same operations, scriptable.