> Den 09/06/2015 kl. 18.54 skrev Alexey Grigoriev :
>
> I found this issue in my big project. And then I started new Django project
> from scratch, and reproduced the problem.
> You can reproduce this bug:
> 1) start new Django project
> 2) create context processor that raises Http404
> 3) se
I found this issue in my big project. And then I started new Django project
from scratch, and reproduced the problem.
You can reproduce this bug:
1) start new Django project
2) create context processor that raises Http404
3) set Debug=False
4) create custom '404.html' template
And then you get
have you written the handler correctly?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send em
Maybe it does not find your custom 404.html (and gives you a 500 of not
finding it)?
Try to use this template elsewhere with debug=True, just to see
On Tuesday, June 9, 2015 at 1:22:44 PM UTC+2, Alexey Grigoriev wrote:
>
> Django doesn't catch django.http.Http404 exception in my context proc
Django doesn't catch django.http.Http404 exception in my context processor
when Debug=False and when I have custom '404.html' template. It just throws
Internal Server Error. Is it Django bug?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
5 matches
Mail list logo
