↑ ↓ to navigate
↵ to select
esc to close
v0.15.1 Feature

v0.15.1 - Redirect rules

Redirect rules send an exact path or a whole path prefix to another URL, including another host, optionally per domain.

New

  • Redirect rules, in Content → Redirects and via the redirect_rules_list, redirect_rules_get, redirect_rules_save and redirect_rules_delete MCP tools. A rule catches from_path exactly or as a prefix (default) and sends it to a site-relative path or an absolute URL on any host, preserving the remainder of the path.
  • A rule may be restricted to one domain, so example.org/docs/* can redirect to docs.example.org/docs/* without firing on the destination host.
  • Status is 301 or 302 (default 302); rule-driven redirects send Cache-Control: no-store. Loops (self, prefix and cycles) are refused at save time.
  • Rules apply wherever a request would otherwise 404: pages, assets and feeds. Unpublished entries and root-routing misses are not redirected.

Changes

  • docs/routing.md corrected: renaming an entry's handle already creates an automatic redirect from the old URL; manual rules are for everything else.