Ship & Quality · LOCAL TOOL
Route Collision Review
Review a list of literal site paths using independently selectable case sensitivity, trailing-slash handling, and percent-decoding rules. Each collision keeps its original source line.
No API call
Your input
LOCALResult
Run the tool to see a result.
Your result will appear here. Input is not saved.
WHY THIS TOOL EXISTS
A focused job, not a black box.
Changing one normalization rule shows which URLs could collapse in a deployment that uses that policy. The report never assumes that every server treats paths the same way.
How to use it
- Paste site paths without domains, queries, or fragments.
- Choose the normalization rules used by your target environment.
- Review each collision group and the original paths that produced it.
TRY A WORKING EXAMPLE
Start with known input.
Load this sample into the workspace, run the tool, and compare the result shown below.
Show sample input
{
"routes": "/Tools\n/tools/\n/docs/%61\n/docs/a",
"caseMode": "Ignore case",
"slashes": "Ignore trailing slash",
"encoding": "Decode percent escapes"
}Expected sample result from the local tool
2 collision group(s) under the selected rules.
{
"routeCount": 4,
"uniquePaths": 2,
"collisions": [
{
"normalized": "/tools",
"routes": [
{
"line": 1,
"source": "/Tools"
},
{
"line": 2,
"source": "/tools/"
}
]
},
{
"normalized": "/docs/a",
"routes": [
{
"line": 3,
"source": "/docs/%61"
},
{
"line": 4,
"source": "/docs/a"
}
]
}
]
}Literal path comparison only. Dynamic route precedence, server rewrites, and dot-segment normalization are not inferred.
LIMITS AND INTERPRETATION
What the result cannot tell you.
Literal paths only. It does not model dynamic parameters, framework route ranking, dot segments, redirects, or actual server behavior. Percent decoding can intentionally expose encoded-slash collisions.
Inputs are processed in this page and are not written to local storage.