53 chars · 1 line
37 chars · 4 lines
53 chars · 1 line
37 chars · 4 lines
URL query and fragment behavior
A URL fragment begins at # and is a separate URL component from the query. Query parsing therefore reads parameters before the fragment and does not expose the fragment as a key or value. This tool is free to use. No account or payment is required.
Last updated
The query begins after ? and ends before #. The fragment identifies a client-side location or state and is not part of the query parameter collection.
If a literal # belongs inside a parameter value, it must be percent-encoded so it is not interpreted as the fragment delimiter.
Only q and lang appear in the parsed output.
https://example.com/search?q=vetatool&lang=en#results{
"q": "vetatool",
"lang": "en"
}Common questions
No. It is the URL fragment.
The fragment is normally handled client-side and is not part of the HTTP request target sent to the server.
Percent-encode it as %23 inside the parameter value.
Debugging a specific Query String issue? Browse Query String troubleshooting.