#15690: HttpRequest path should be in a stable order
------------------------------------------+----------------------
Reporter: jdunck | Owner: nobody
Status: closed | Milestone:
Component: Core framework | Version: 1.2
Resolution: invalid | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
------------------------------------------+----------------------
Changes (by lukeplant):
* status: new => closed
* resolution: => invalid
Comment:
No - they should leave the query string in the same order as the browser
specified, because changing the order can potentially change the meaning
of the query. That might be unusual, but I'm not aware of any RFC that
would forbid it. In fact there is no requirement that a querystring has to
be name value pairs at all - that is how they are used by browsers for
encoding GET forms, but there is no HTTP requirement that they should be
used that way. At this level, Django should be treating the query string
as opaque.
Trac happens to use URLs where the order of query parameters matters a lot
e.g.
[http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&has_patch=0&stage=Accepted&or&status=new&status=assigned&status=reopened&needs_better_patch=1&stage=Accepted&or&status=new&status=assigned&status=reopened&needs_docs=1&stage=Accepted&or&status=new&status=assigned&status=reopened&needs_tests=1&stage=Accepted&order=priority
this report]
--
Ticket URL: <http://code.djangoproject.com/ticket/15690#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
