Re: lighttpd + fcgi + FORCE_SCRIPT_NAME = admin grief

2008-08-22 Thread James Matthews
Nick, The issue is with the url rewrite. while django puts in the script name lighttpd cannot read it because it's rewirting the url. E.g my FCGI script is mysite.fcgi and when i tried going to the django admin interface i would get a link like http://mysite.com/mysite.fcgi/adminhowever lighttpd

Re: lighttpd + fcgi + FORCE_SCRIPT_NAME = admin grief

2008-08-21 Thread Nick
Hi Malcolm, Great; James' suggestion does work perfectly (stupidly obvious; it was of course the one thing I hadn't tried) as suggested. If you're trying to figure out how I got to this recipe I blindly followed the instructions here:

Re: lighttpd + fcgi + FORCE_SCRIPT_NAME = admin grief

2008-08-21 Thread Malcolm Tredinnick
On Thu, 2008-08-21 at 10:02 -0700, James Matthews wrote: > Try FORCE_SCRIPT_NAME="" I use it and it works nicely It's always interesting after landing a feature like this that has a few edge cases to see where the problems distribute themselves. Turns out there are a lot of people using the

Re: lighttpd + fcgi + FORCE_SCRIPT_NAME = admin grief

2008-08-21 Thread James Matthews
Try FORCE_SCRIPT_NAME="" I use it and it works nicely James On Thu, Aug 21, 2008 at 9:00 AM, Nick Clarey <[EMAIL PROTECTED]>wrote: > > Hi all, > > I've been getting my site ported over to 1.0 beta and ran into a > problem. Basically everything works fine when I follow the > instructions

lighttpd + fcgi + FORCE_SCRIPT_NAME = admin grief

2008-08-21 Thread Nick Clarey
Hi all, I've been getting my site ported over to 1.0 beta and ran into a problem. Basically everything works fine when I follow the instructions except logging into the admin site. The source for the admin login page shows that the login form submits data to "//admin/"; Which is obviously not