2009/10/24 msoulier <[email protected]>: > > Hi, > > Apologies if this has been answered. > > I'm moving from mod_python for django hosting in apache to mod_wsgi. I > have it working, but I did have to update my urlconf, and I'm not > ensurely sure why. > > One access my app in an existing, legacy site via a url like > > /manager/django/myapp > > When in mod_python, the /manager/django/myapp is seen by the django > app so I had to have that as a prefix on all my urls in the urlconf (I > put it in a variable called baseurl). > > Moving to mod_wsgi I notice that this is no longer true, and baseurl > is now /. > > I'm not against that but I am trying to soften the blow of the move > for existing apps moving, so I was curious as to why this is > different, and if there is any option to maintain the existing > behaviour.
The mod_python package as well as way Django interacted with it was broken in as much as identify the mount point correctly when mounting at a sub URL. Django 1.0 fixes this but still necessary to set a mod_python variable to tell Django where it is mounted as mod_python doesn't generate that location properly. The mod_wsgi module doesn't have these problems and Django honours the SCRIPT_NAME variable giving the mount point and so things work without needing to mentioned mount point in urls.py. This is mentioned briefly in: http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
