I had the same problem as Gonzalo, using lighttpd, looked at the BackwardsIncompatibleChanges link, and tried FORCE_SCRIPT_NAME="/" in my settings.py. Unfortunately, that seems to create a different problem: after going to my site's admin and logging in, I see the browser trying to load "http://admin/";. Obviously that doesn't work very well.
Luckily I can type in the right URL after that and I get to the site admin, successfully logged in. But it would be good to fix this for users. If anybody can just suggest a fix that would be great. If not, any pointers to where I can read more about lighty's use of URLs and Django's use of URLs would help. Thanks, Lisa On Aug 18, 12:55 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Mon, 2008-08-18 at 16:47 -0300, Gonzalo Almeida wrote: > > hello, > > I have a problem with lighttpd + fastcgi, > > I used have the newforms-admin branch and everything worked fine. > > but when I started using the trunk version, the problems appeared. > > when I accesshttp://localhost/admin/, I try to loggin in the admin. > > and it redirect me tohttp://localhost/mysite.fcgi/admin/ > > and this appear in the browser : > > > Page not found (404) > > Request Method: POST > > Request URL: http://localhost/mysite.fcgi/mysite.fcgi/admin/ > > (the mysite.fcgi is repeated) > > Refer > tohttp://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Chang... > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
