Match conditions
- HTTP method.
- Exact, contains, wildcard, or regular-expression URL matching.
- All pages or a specified set of page origins.
- The first matching rule in the current order wins.
Enablement
- Request interception must be enabled for the current site or all sites, and the rule itself must be enabled.
- A root-level rule does not need a group.
- For a grouped rule, its group and every parent group must be enabled.
Request stage
Rewrite query, payload, and headers that browser extensions are allowed to modify before delivery. Browser-managed headers are not forged.
Route stage
Continue, redirect, or cancel. Redirect cooperates with the native network layer and cannot be combined with incompatible request or response actions.
- If the target URL has a query, the target query wins.
- If it has no query and Preserve original request query is on, Reqix appends the original query.
- If it has no query and the switch is off, the original query is omitted.
Response stage
- Return the upstream response.
- Return a static status, headers, and body.
- Generate response data with a dynamic script.
- Rewrite response headers or delay delivery.
Potential conflicts
Reqix warns when another rule may match the same request. Saving does not delete or overwrite existing rules; the first match in the current order still wins at runtime.