parseQuery string DOES need a switch for what to do when encountering two keys of the same value. PHP expects such things to be expressed as foo[]=bar&foo[]=baz and our query string utilities do this. But I've had to overwrite this function any time I'm using a backend other than PHP. The other way, which is really the proper way, is that everything but PHP expects duplicate keys: foo=bar&foo=baz which, like PHP, gets turned into an array on the back end. parseQuery should have an option to behave this way (and the query encoding code we have as well).
Regarding the HTML entities, you should run your url through a replacer that swaps out & for & before parsing it. On Tue, Feb 7, 2012 at 10:39 AM, Sanford Whiteman <[email protected]>wrote: > > 'amp': ['', ''], > > 'Expires': '1330162525', > > 'Signature': 'F/bNMruOog2ejsspsaZTBKVkIHM=' > > } > > > (which is what it is now, judging from the "[2]"?) > > I presumed that now it's interpreting each name-no-value as if it were > a boolean true, then [true + true] = 2. Obviously that would please > few. :) > > -- S. > >
