> your browser will submit: > https://www.google.com/?foo=1&foo=2&bar=1&bar=2
> This isn't a backend doing the encoding; this is your browser sending a GET > request. This is how things *normally* work. Did I question this somewhere? I don't think so... The question is whether a client-side QS parser should have one, two, three, or perhaps zero `hints` available as to how it builds its returned object. You said it's standard for CGIs other than PHP to parse `foo` into an array. That is simply not true. There are three major approaches (discard, explode, concatenate) and more servers in-the-wild running CGIs that *don't* explode the above into an array than CGIs that do. -- S.
