URL query / duplicate key / array convention

Separate URL query duplicates and array meaning

Review duplicate query keys, bracket arrays, plus signs, order and fragment boundaries with synthetic cases. User URLs are never accepted; save a local review note instead.

Five URL query boundaries

Same-name query keys are handled differently by servers and libraries. Record array notation, decoding, order and fragments separately.

same key ≠ one value / query → array → verify
AxisReview
duplicateDo not silently collapse duplicate query keys to the last value.
bracketitems[]=a is a convention, not a universal specification.
plusSeparate plus-as-space from a literal plus sign.
orderKeep order when a server gives it meaning.
fragmentA fragment is separate from the query and is not sent to a server.

Safe review order

  1. Record duplicate keys and order in a synthetic query.
  2. State the interpretation of brackets and plus signs.
  3. Separate the fragment boundary before handing values off.
  4. Approve the local note before returning to a real URL.

This page never parses user URLs. It uses synthetic cases only and performs no external request, storage or URL rewrite.

Six synthetic cases

caseresult
duplicate-keysPreserve duplicate values
bracket-arrayBracket convention
plus-decodingPlus boundary
order-preservedKeep order
fragment-boundaryFragment is separate
local-noteLocal handoff