On Mon, Jan 2, 2012 at 11:39 AM, Dan Poirier <poir...@pobox.com> wrote:
> Apache doesn't quite work that way. If the part before a slash > corresponds to a file, it'll use that file and pass the rest to the > request processor. Ah, very clever. I can confirm what you say by changing the AddHandler directive from AddHandler fcgid-script .fcgi to AddHandler cgi-script .fcgi So, when Apache was telling me (when the first version of the AddHandler directive was in play) "The requested URL "/appname.fcgi/admin was not found on this server" (the error message leading me to the incorrect conclusion that Apache interpreted the file path syntax the same way Unix does) what it really meant was "your hosting provider hasn't set up mod_fcgid properly." Odd way to communicate that problem. So I guess I'll have to go back to my hosting provider and ask why this isn't working, in spite of documentation on their site implying that it should. Thank you very much for getting me unstuck from the misleading Apache error message. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
