All spotlights

Product spotlight · May 2026

Redirect trailing slashes and purge by cache key on QuantGov and in CI

You can now redirect static paths that end in a slash, purge by cache key on QuantGov, and purge by key without a URL from the CLI and GitHub Actions.

Updated Global CDN For government and enterprise

What changed in May 2026

The May 2026 changelog has the full details.

  • Trailing-slash redirects

    Projects have a new "Redirect trailing slashes" option in the create and settings forms. When it is on, a request for a path such as /about/ gets a permanent (301) redirect to the same path without the slash. The redirect applies to static content that Quant serves, not to requests that a proxy rule handles. New projects have the option on, and existing projects keep their current behaviour until you turn it on.

  • Cache-key purge on QuantGov

    You can now purge by cache key on QuantGov projects, from the dashboard purge form and the API. One request invalidates all content tagged with a shared key. Soft purge is still not available for QuantGov projects.

  • CLI purge by key only

    The quant purge command no longer needs a URL path. Run it with only --cache-keys to purge by key. You cannot combine a path and --cache-keys in one command. This is available from CLI v6.2.0.

  • Purge action inputs (v7)

    The GitHub purge action has two new inputs. cache_keys purges by cache key instead of URL pattern. soft_purge marks content stale, so it is served until fresh content is available. url_pattern is now optional and cannot be combined with cache_keys.

By the numbers

permanent redirect for a trailing slash
301
purges by cache key with no path
CLI v6.2.0
adds cache-key and soft purge inputs
Action v7

Who it is for

  • Government teams

    QuantGov projects can now purge by cache key, so one request invalidates all content that is tagged with a shared key.

  • Site owners

    Turn on trailing-slash redirects, so static content at a path that ends in a slash goes to the path without the slash.

  • CI pipeline owners

    Purge by cache key in a CI pipeline, from the CLI with no URL path or from the GitHub purge action with cache_keys.

How it works

The trailing-slash redirect is a project setting. When “Redirect trailing slashes” is on, a request for /about/ gets a permanent (301) redirect to /about. The redirect applies only to static content that Quant serves. Requests that a proxy rule handles are not redirected. New projects, including projects created through the API, have the option on by default. Existing projects keep their current behaviour until you turn it on.

A cache-key purge works on content that your origin tags. Your origin sends a Cache-Keys header with the response. One purge request then invalidates all content tagged with a shared key. May adds these ways to send that request:

  • On QuantGov projects, from the dashboard purge form and the API.
  • From the CLI, with only --cache-keys and no URL path.
  • From the GitHub purge action v7, with the cache_keys input.

For example, a CI step can purge by key without a path:

quant purge --cache-keys <keys>

In the purge action, set soft_purge to mark content stale. The stale content is then served until fresh content is available. Soft purge is not available for QuantGov projects.

Get started

  1. Turn on the redirect

    In your project settings, turn on the "Redirect trailing slashes" option.

  2. Tag your responses

    Send a Cache-Keys header from your origin on the content that you want to group.

  3. Purge in the dashboard

    Use the cache key field in the dashboard purge form.

  4. Purge from the CLI

    Use quant purge with --cache-keys, from CLI v6.2.0.

  5. Purge from GitHub Actions

    Set cache_keys in purge action v7. Read Scoping the purge.

Related: Explore Global CDN · Documentation · May 2026 changelog

Ready to try it on Quant?

Use the global CDN on your own project, or talk to our team first.