🎯 Route Matcher

Edit the route table or the request and watch which route wins, why the others lose, and which parameters are extracted. Routes are tried in registration order, exactly like in a real Fiber app:

#	Method	Pattern	Result	Remove
1	GETPOSTPUTDELETEPATCHQUERYALL		path has an unmatched remainder "users/42"
2	GETPOSTPUTDELETEPATCHQUERYALL		static part "/users/new" does not match at "/users/42"
3	GETPOSTPUTDELETEPATCHQUERYALL		matches, first match wins
4	GETPOSTPUTDELETEPATCHQUERYALL		not tried, an earlier route already matched
5	GETPOSTPUTDELETEPATCHQUERYALL		not tried, an earlier route already matched
6	GETPOSTPUTDELETEPATCHQUERYALL		not tried, an earlier route already matched

Request:GETPOSTPUTDELETEPATCHQUERY

200 OK

Route 3 answers: GET /users/:id<int>

Parameter	Value
id	42

Simulates Fiber's matcher with default settings (case-insensitive, non-strict routing). Verified against the real matcher; datetime and custom constraints are not simulated, and regex() runs on the JS engine.

note

The playground simulates Fiber's matcher with default settings (case-insensitive, non-strict routing). datetime and custom constraints are not simulated, and regex() runs on the JS engine instead of Go's RE2.

The routing guide explains the full syntax: parameters, wildcards, literal separators, and constraints.