On Donnerstag, 5. April 2007, Bram - Smartelectronix wrote: > Malcolm Tredinnick wrote: > > This looks correct. Not sure why it isn't working, sorry. If you wanted > > to do some more poking around, we set up PATH_INFO in > > django/core/handlers/modpython.py, so you could put some debugging in > > there to see what the value we get from modpython is. I'm reluctant to > > think this would be a modpython problem, either ...something strange is > > going on though. I don't really have any obvious ideas about what could > > be going on here. > > That was easy to test and it does look like mod_python is giving us the > wrong path_info! > > We're going to try switching off EVERYTHING in the apache config and add > it back bit by bit to see what the hell is provoking this weird error. > > I'll report back later!
Hi, i had a very similiar problem once. It turned that i had a "DocumentRoot" defined in my vhost config and that caused weird PATH_INFO problems. Django doesn't care about the DocumentRoot (IMHO), so i just removed it, but it took me quite a while to figure that out. I can't see anything unusual in your config though... Best Regards, Dirk Eschler -- Dirk Eschler <mailto:[EMAIL PROTECTED]> http://www.krusader.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
