On 10/16/06 20:27, DavidA wrote: > > Steven Armstrong wrote: >> Have you got a folder/file named 'data' in your apaches document root? >> If so, try nuking or renaming it. > > No. And no virtual directories or aliases named 'data' either, nor a > file or folder named 'data' in my django project directory. > > Note that the page URL is working (http://web/data/pos/) correctly > under both Apache and the development server. Its just that I can't > generate the correct URL for my next/prev links under Apache because > that path is not correct. > > -Dave >
Pitty that didn't work. I've had similar problems with mod_python and in my case it was apache being confused because of a folder with the same name in document root. After renaming the folder everything was fine. Anyway it seems like this is a common problem with mod_python [1], [2]. The trac devs have also bumped into this. They solved it by explicitly passing the base url with a PythonOption [4]. Same as the MoinMoin devs [3]. Googling for 'mod_python path_info' turns up loads of similiar questions/problems/solutions. Probably a mechanism like that [5] could/should be built into djangos mod_python handler. [1] http://mail.mems-exchange.org/durusmail/quixote-users/3250/ [2] http://www.modpython.org/pipermail/mod_python/2003-July/013948.html [3] http://moinmoin.wikiwikiweb.de/HelpOnInstalling/ApacheWithModPython [4] http://trac.edgewall.org/ticket/552 [5] http://trac.edgewall.org/changeset/797 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
