46 chars · 1 line
64 chars · 4 lines
2 parameters2 unique keys
46 chars · 1 line
64 chars · 4 lines
Nested URL query parameter
When a redirect or callback URL is placed inside another query string, its raw ampersands are indistinguishable from the outer query separators. Percent-encode the embedded URL so it remains one value. This tool is free to use. No account or payment is required.
Last updated
In ?redirect=https://example.com/callback?a=1&b=2, the raw & starts a new outer parameter named b.
When the redirect value is percent-encoded, its %26 and %3D sequences are decoded only after the outer parameter boundary has been established.
The inner b=2 becomes a separate outer parameter.
?redirect=https://example.com/callback?a=1&b=2{
"redirect": "https://example.com/callback?a=1",
"b": "2"
}Common questions
The first raw & is interpreted as the next outer query parameter separator.
Encoding the whole nested URL as one query-component value is usually safer than manually escaping individual delimiters.
Yes. Any complete URL nested inside another query value needs component-safe encoding.
Debugging a specific Query String issue? Browse Query String troubleshooting.