Exactly for your case, you may set LOGIN_URL point to '/myapp/accounts/login/', but 'next' parameter still left inaccurate. http://docs.djangoproject.com/en/dev/ref/settings/#login-url
For more general case, to make working not only auth urls, look at those snippets: - http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango - comment section, look around URL_PREFIX keyword; - http://opensourcemissions.wordpress.com/2010/03/12/finally-a-working-django-non-root-url-with-mod_wsgi/ On Jul 7, 2010, at 3:12 AM, Jacob Fenwick wrote: > I'm deploying my Django app on Apache using mod_wsgi. > > The app is using a non-root mount point. > > So instead of accessing it as: > http://server.com/ > > I access it as: > http://server.com/myapp/ > > When I navigate to a url that requires logging in, I get redirected, but my > mount point is dropped, e.g.: > http://server.com/accounts/login/?next=/articledist/publish/ > > But I should be redirected to: > http://server.com/myapp/accounts/login/?next=/articledist/publish/ > > If I manually navigate to the correct url it comes up. I'm even able to login > correctly. > However, this is obviously not an acceptable solution. > > Why is this happening? > > -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
