Feature

Redirect rules

SecureRedirector resolves incoming requests through a small set of clear rules. No DSL, no surprises — just match by what's in the request and pick a destination.

The rule types

• Domain rules. Per-domain default destination — every request to brand-a.com goes one place, every request to brand-b.com goes another.
• Port rules. Useful when one host serves multiple services on non-standard ports.
• Path rules. Match on path prefix — /promo/* goes one place, /support/* goes another.
• Short links. An optional table of slug → URL lookups, applied before the rule engine. Use when you need a Bitly-style flow on top of rule-based routing.

Resolution order

1. If short links are enabled and the slug matches, redirect.
2. Match a port-specific rule, if one exists.
3. Match a path-specific rule, if one exists.
4. Fall back to the domain's default destination.

Permanent vs temporary

Pick the HTTP status per rule. Use 301 when the destination is canonical (it passes link equity for SEO) and 302 when the destination is temporary.