On Aug 2, 6:11 pm, Giorgio Salluzzo <[EMAIL PROTECTED]> wrote: > On Jul 31, 12:25 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > Huh. What bug, strange behaviour in mod_python? What old threads? > > Excuse me, I tought he was having a problem similar to the > following:http://www.modpython.org/pipermail/mod_python/2003-July/013947.html > > We had the same and I tried to solve it before deciding to take other > deployment decisions.
The behaviour exhibited in that post on mod_python list is perfectly normal for Apache and is just how Apache works. This strangeness of Apache in the way mod_python handlers works is part of the reason why SCRIPT_NAME for a WSGI application cannot be automatically determined by WSGI adapters for mod_python. The only easy way SCRIPT_NAME can be worked out properly is by doing script determination from a transhandler. To do such a thing in Python, because all requests for the virtual server go through Python code, would unnecessarily slow down request handling. FWIW, because mod_wsgi is all in C code it doesn't have this problem and can work out SCRIPT_NAME properly by using a transhandler. Either way that strangeness should not have been an issue as from memory Django just uses req.uri directly and is not dependent on req.filename or req.path_into. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
