Route Pattern Overlap Audit
Find pairs of supported route patterns with a matching method and show a path that fits both.
Switching language or leaving this page discards the current draft.
Input
One route per line: HTTP method, one Tab, then the path pattern. For example GET, one Tab, /users/:id.
Supported parameter and tail syntax
A pattern starts with / and has at most 8 segments, with no trailing slash. Literals use lowercase letters, digits, - and _ only (for example users, new, v2). A parameter is written :name (for example :id); a tail is written *name and may only be the last segment (for example *rest, which matches at least one segment). Parameter and tail names must be unique within one pattern. Methods must be uppercase GET, HEAD, POST, PUT, PATCH, DELETE, or OPTIONS; GET and HEAD never overlap.
Not run yet. Enter routes or load the example.
Overlapping pairs and example paths
Each row is a pair of routes that can match the same path; the witness is a path that fits both.
No overlapping routes: no two patterns with the same method share a matching path.
| Method | First route | Second route | Example path |
|---|
Frequently asked questions
- Does this say which route wins?
- No. It provides a path that fits both patterns. Your framework determines precedence.
- Can a tail match zero segments?
- No. This profile requires at least one segment.