#3414: middleware/common.py and SCGI bug - string index out of range
-----------------------------------------------------------+----------------
Reporter: Piotr Maliński <[EMAIL PROTECTED]> | Owner:
nobody
Status: reopened | Milestone:
Component: Core framework | Version:
SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------+----------------
Comment (by mtredinnick):
The setup being espoused in comment 16 looks like a terrible way to set up
a webserver. I'm not sure we really want to pollute the main code with
anything extra just to handle that case. It's using a 404 error path to
try and do normal (non-error) handling. The Django docs already explain
how to use lighttpd with fastcgi without needing to corrupt an error
handler that is intended for an entirely different purpose.
Fortunately, it won't be impossible to work this way, since you can always
subclass the WSGI handler and write your own handler for this situation
which is even further from a proper WSGI environment than Django normally
expects. But I doubt that I'm going to include this in core right at the
moment, since it's not an approach we should be encouraging and it's a lot
of extra poking into environment variables to work around something (and
we would have to maintain it forever).
--
Ticket URL: <http://code.djangoproject.com/ticket/3414#comment:17>
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
-~----------~----~----~----~------~----~------~--~---
