WORKED EXAMPLE · SYNTHETIC INPUT
Find changed and repeated URL query parameters
A search link behaves differently after being copied between environments. Looking only at a dictionary of query keys can hide repeated values, while comparing raw text can overstate differences in space encoding.
These inputs demonstrate reproducible behaviour; they are not customer incidents or evidence of real usage.
Reproducible input
https://example.com/search?q=hello+world&tag=red&tag=blue
Steps
- Load this example in the URL comparison tool. The right sample reverses the tag values, moves q and adds page=2.
- Compare URLs: q decodes to ["hello world"] on both sides. tag changes from ["red","blue"] to ["blue","red"], and page is added.
- Set URL B to https://example.com/search?q=hello%20world&tag=red&tag=blue and compare again. Decoded groups and sequence now match, but the original text still differs.
- Change hello%20world to hello%2Bworld. q now differs because %2B is a literal plus, not a space.
Expected result
The first comparison reports changed tag values, an added page and unchanged q. An absent parameter is [], while an explicitly empty value is [""]. Repeated values are never collapsed to the last value.
Limits and manual checks
This local tool does not contact either server. Browser parsing normalizes host names and default ports; decoded equality cannot prove server equivalence or signature validity. No-equals and empty-value parameters decode identically. Malformed query escapes are rejected. Reports include parameter values, so inspect them before sharing.
Technical reference