URL Query Key Repetition Summary
Summarize query-name repetition in first-seen order and retain all decoded values, including empty values.
Description
Summarize query-name repetition in first-seen order and retain all decoded values, including empty values.
Repeated query keys can collect several ordered values after form-style decoding. Raw spellings may differ while decoded names match.
When to use this tool
Summarize query-name repetition in first-seen order and retain all decoded values, including empty values.
- Prepare the supplied query fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter query. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.keys. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Remove one optional leading question mark, reject a fragment and ignore empty ampersand fields. Split each remaining field at its first equals sign, decode plus as space and percent escapes as UTF-8, then group names with counts and ordered values.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| query | query. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.keys | The keys list in the ordering and representation described above. |
{
"input": {
"query": "a=1\u0026a=2\u0026b="
},
"output": {
"result": {
"keys": [
{
"name": "a",
"count": 2,
"values": [
"1",
"2"
]
},
{
"name": "b",
"count": 1,
"values": [
""
]
}
]
}
}
}Limitations and assumptions
- Malformed escapes are errors. Names are case-sensitive; no Unicode normalization, dictionary last-wins policy or full URL parsing occurs.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a complete protocol or URL parser when interpreting a whole message or address. Preserve raw spelling when required and distinguish HTTP token grammar, URL path normalization and form-style query decoding.
References
Similar or alternative tools
- URL Query Key Collision Audit
Audit query-name collisions after form-style percent decoding; encoded spellings and duplicate source positions remain visible.
- url query count
A query is an ordered collection of name/value entries and may repeat a name.