On Tue, Jun 8, 2010 at 2:56 PM, adrian <adrian.imm...@gmail.com> wrote:
> tracked the problem more down... > > the problem appeared when using own handler404/handler500 views and > returning the invalid HttpResponse instead of HttpResponseNotFound/ > HttpResponseServerError. This is not documented and needs doc > improvement ... > > Directly from http://docs.djangoproject.com/en/dev/ref/contrib/flatpages/: > The middleware only gets activated for 404s – not for 500s or responses of > any other status code. It really is not good practice to convert a 404 or 500 error to a proper response. Google just recently released a tool on web master tools that shows you what they call soft 404s. These are urls that should return a different response than 200, but yet still do. If this is what you need to do you should look at the FlatPageFallBackMiddleware and change the times that is activated. Hope that helps, Michael -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
