Re: Why do the fastcgi instructions for Apache include a RewriteCond for file existance?

2012-10-04 Thread Dino Viehland
On Thursday, October 4, 2012 1:41:59 AM UTC-7, Tom Evans wrote: > > The FastCGI 'file' is not a real file, nor is it part of your project > code. Instead, it is a URL location that your requests can be routed > through if they are to be served by the web application specified by > the 'file'.

Re: Why do the fastcgi instructions for Apache include a RewriteCond for file existance?

2012-10-04 Thread Tom Evans
On Thu, Oct 4, 2012 at 1:17 AM, Dino Viehland wrote: > Looking at the instructions for how to use Django w/ shared hosting via > FastCGI at > https://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/#running-django-on-a-shared-hosting-provider-with-apache > it includes this line: > > Rewrite

Why do the fastcgi instructions for Apache include a RewriteCond for file existance?

2012-10-03 Thread Dino Viehland
Looking at the instructions for how to use Django w/ shared hosting via FastCGI at https://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/#running-django-on-a-shared-hosting-provider-with-apache it includes this line: RewriteCond %{REQUEST_FILENAME} !-f That will cause the web server