On Sep 5, 8:59 pm, Michael Radziej <[EMAIL PROTECTED]> wrote: > On Wed, Sep 05, Thomas Guettler wrote: > > > Am Mittwoch, 5. September 2007 11:27 schrieb Michael Radziej: > > > On Wed, Sep 05, Thomas Guettler wrote: > > [cut] > > > Is this the same problem as in ticket #285? > > > >http://code.djangoproject.com/ticket/285 > > > Yes > > Great - Thomas, could you test the patch that is attached to the ticket? > > Is there a general agreement that the mod_python path is the correct one?
Be very very cautious about accepting that how mod_python does things is correct. This is because the way that mod_python works means that it doesn't set SCRIPT_NAME/PATH_INFO correctly most of the time. All WSGI adapters for mod_python have to fudge it, by allowing a user to say what SCRIPT_NAME should have been and then the WSGI adapter tries to then work out what PATH_INFO should have been based on that. Since SCRIPT_NAME/PATH_INFO derive from CGI behaviour, you would be much better looking at what a CGI script produces and work things out from there. Alternatively look at what mod_wsgi produces as it correctly mirrors what normal CGI would produce for SCRIPT_NAME/PATH_INFO. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
