W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 20148] URLQuery interface does not handle query parameter ordering

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Nov 2012 05:07:35 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20148-2532-uIQ2fHH2Yp@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20148

--- Comment #2 from Simon Kaegi <simon_kaegi@ca.ibm.com> ---
(In reply to comment #1)
> Ordering isn't lost; it's just not exposed by the "get" method.  getAll lets
> you access the less common cases: repeated keys, significant ordering, and
> when you have elements that aren't key=value.  (A system I've used now and
> then is "http://url.com?foo/bar&x=y", where the first parameter is treated
> like a path.)

Hmm... perhaps I'm misunderstanding the intent of the api.

I can see how "getAll" supports repeated keys and perhaps value ordering for
the repeated key case but not overall ordering. e.g. How do I use getAll to get
the first query parameter?

Also, when outputting a URL how do I control parameter ordering for
serialization. This matters (I believe) because http://url.com?a=b&c=d and
http://url.com?c=d&a=b are treated as different URLs for caching purposes.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 29 November 2012 05:07:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 November 2012 05:07:37 GMT