Manage redirect rules with precision

The rules management system provides a visual editor for creating redirect rules without writing server configuration files. Each rule defines a source path, a destination URL, a match type, and an HTTP status code.

Source patterns support two matching modes: exact match for specific URLs, and prefix matching (starts_with) for handling entire path hierarchies. Exact matches use O(1) hash lookups at the edge, while prefix matches are evaluated in order of path length for deterministic behavior.

When you save rules through the editor, they are validated for duplicate source patterns and potential conflicts before being stored. The validation engine catches common mistakes like duplicate sources or invalid paths before they reach production.

The visual rule editor is designed for teams that manage redirect rules collaboratively. Each rule includes metadata fields for notes, tags, and labels, making it easy to understand why a rule exists months after it was created. Rules can be filtered and searched by any field, so finding the rule responsible for a specific redirect is instant.

Bulk operations let you select multiple rules and apply batch changes — enable, disable, or change status codes. This is especially valuable during large migrations where you need to activate hundreds of rules simultaneously after testing them.

The matching system uses two modes: exact matches for specific URLs and prefix matching for entire path hierarchies. Exact matches are evaluated first via hash lookup, followed by prefix matches sorted by path length. This gives you predictable, deterministic redirect behavior.