#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
-------------------------------------+--------------------------------------
Reporter: mtredinnick | Owner: mtredinnick
Status: assigned | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* owner: nobody => mtredinnick
* needs_better_patch: => 0
* status: new => assigned
* needs_tests: => 0
* needs_docs: => 0
Comment:
I want to make sure we at least look at this. It may or may not be an
actual issue, since Django's URL resolver doesn't care about the leading
'/'; it just treats it as a separator and there must be some kind of
"first character" in the URL. So I suspect it's probably not actually
causing any misbehaviour and we're just ensuring the `PATH_INFO`
equivalent is in a reasonably normalised form. However, we should make
sure that the reported information (via `request.path_info`) matches
reality, which may be an empty string, so that means differentiating
between our internal normalised version and the upstream passed-in
version.
--
Ticket URL: <http://code.djangoproject.com/ticket/9435#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
-~----------~----~----~----~------~----~------~--~---
