Tester

The Tester lets you simulate an HTTP request and see exactly how the rule engine evaluates it — which rules were checked, why they matched or were skipped, and what the final redirect would be.

Input fields

Field	Description
Method	HTTP method (GET, POST, PUT, DELETE)
URL	Host, path, and query string in one field, e.g. example.com/shop/42?lang=nl
HTTPS	Whether the request uses HTTPS (Scheme = "https") or HTTP
Headers	One Name: Value pair per line
Cookies	One Name: Value pair per line
Geo Country	ISO 3166-1 alpha-2 country code override, or Unknown to simulate an unresolvable IP
Geo Continent	Continent code override, or Unknown
Returning Visitor	Simulate a visitor with a known marker cookie

The URL field accepts input with or without a scheme prefix — https:// is stripped automatically if pasted.

Results

After pressing Test, results appear below the form without navigating away.

Match / No match card

Shows the first rule that matched, including:

• Extracted values
• The target template and the resolved redirect URL
• The HTTP status code
• Any cookies that would be set

If no rule matched, a warning card is shown instead.

Parsed request

Shows exactly what the engine received — useful to verify that the URL was parsed as expected (host, path, query, scheme, method).

Evaluation steps

A table showing every enabled rule that was evaluated, in order:

Column	Description
#	Sort order
Rule & Expression	Rule name and its match expression
Result	MATCH, EXTRACT ERROR, or skip
Extracts	Captured values, or amber warnings for map misses
Details	The reason a rule was skipped or that all conditions were met

Diagnosing a map miss

When an extract uses Map() and the key is not in the map, the extract column shows an amber badge and a message such as:

⚠ Map 'products': no entry for key '4'

This is purely a tester diagnostic — in production the rule still applies and the extract value is simply "".