#285: WSGIRequest should set request.path to full uri path
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Milestone: 1.0 alpha
Component: HTTP handling | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by Richard Davies <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
Comment:
I want to make sure that this thread is aware of one use case, which is
unusually behaved, but should be supported.
I run Django with Lighttpd, using the error-handler-404 mechanism borrowed
from the standard Rails config for this web server
(http://github.com/rails/rails/tree/master/railties/configs/lighttpd.conf)
When run in this manner, Lighttpd sets only REQUEST_URI and SCRIPT_NAME
(to the handler!), but neither PATH_INFO nor QUERY_STRING
(http://trac.lighttpd.net/trac/wiki/FrequentlyAskedQuestions#Whatkindofenvironmentdoesserver
.error-handler-404setup)
I have just submitted a patch against #3414 which builds both PATH_INFO
and QUERY_STRING out of REQUEST_URI if they are missing in
WSGIHandler._init_ . It looks like similar code is probably needed in the
eventual patch generated from this thread?
--
Ticket URL: <http://code.djangoproject.com/ticket/285#comment:30>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
