The answer to your question depends in part on how your server is set up. Are you using ModPython or FCGI? If your using ModPython, I would try an Alias instead of a RewriteRule. If your using FCGI try pointing your rewrite rule directly at your fcgi script with the appropriate url as a query string. For that matter an Alias may be better with fcgi as well. Either way, that should get you started.
On 3/14/06, Les Smithson <[EMAIL PROTECTED]> wrote: > > This is probably not a Django problem, but I bet someone knows how > to fix this. > > I have a working Django site, say http://localhost/django/spam. I want to > use the Apache rewrite module to map this to http://localhost/ham. When I use > the RewriteRule, it does the rewrite then tries to look up django/spam in the > local file system (ie /usr/local/apache2/htdocs/django/spam does'nt exist), > ignoring the django handler, so I get a 404. Using > http://localhost/django/spam directly works fine. > > Eg httpd.conf: > > RewriteRule ^/ham /django/spam > <Location /django/spam> > Usual mod_python stuff > </Location> > > > I can make this work using the [R] flag, but that exposes /django/spam to > the browser, which is what I'm trying to avoid. > > > > > -- > Les Smithson <[EMAIL PROTECTED]> > Open Network Solutions Ltd > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQBEFp/1fLQw5akLdfURArXBAJ9GPXZQrZ5cizEp/LKrVpGS76ayaQCgvDXb > r6tIWyoykPh+IUZncSj9jjU= > =8BGa > -----END PGP SIGNATURE----- > > > -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
