[FASTCGI] Django + FastCGI problem
jsprenkle at gmail.com
Sun Dec 7 17:18:41 EST 2008
Is your custom 404 page done as an apache option?
It sounds like it is. If you're using django and it doesn't report it as an
error then apache's error page will, as you've seen, never get invoked. You
need to ask the django developers for the solution here.
On Sat, Dec 6, 2008 at 4:55 AM, <evilhare at yandex.ru> wrote:
> Hi, I am using Django + Apache (via FastCGI).
> I've made my own 404 page (404.html in templates dir) and turned debug
> mode off.
> When I'm requesting for non-existed page I see my custom error page,
> but in Apache's log there is something like this:
> "GET /authors/333.html HTTP/1.1" 200 368 "-" (the return code is 200,
> not 404).
> Also I've tried custom error view (handler404 in urls.py):
> from django.http import HttpResponse
> def handler404(request):
> return HttpResponse('qqq', status=404)
> I see 'qqq' when requesting for non-existed page, but there is still
> 200 code in logs, not 404.
> Guy from the hosting support team told me:
> " the problem here, is that the application is still returning something.
> The web server still displays content from the dispatch.fcgi script (even
> though it's nothing). The 404 comes from within your application, which
> is still running and responding to apache.
> Unfortunately, there's nothing on our end that can be changed to fix
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FastCGI-developers