#11903: WSGIRequest.path not quoted properly
-------------------------------------+-------------------------------------
Reporter: ianb | Owner: fgallina
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* ui_ux: => 0
* resolution: => invalid
* easy: => 0
Comment:
I believe the current behavior is correct. Django handles the encoding /
decoding wherever necessary and provides `unicode` objects to the
programmer.
`request.path` is `unicode` and has no reason to be url-encoded. (In the
code quoted in the original report, `path_info` is `unicode`, which
guarantees that `self.path` is `unicode`.)
This is a custom API of Django, which means we aren't bound by the WSGI or
CGI spec there (while we are for `request.META['PATH_INFO']`).
To sum up, if I'm typing "www.mysite.com/foo bar/" in my browser, the
browser will issue a request for "/foo%20bar/", but Django will convert
that back to `u"/foo bar/"`.
--
Ticket URL: <https://code.djangoproject.com/ticket/11903#comment:13>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
