#30475: Use of i18n_patterns and a buggy 404 template trigger internal server
error
without a backtrace.
-----------------------------+--------------------------------------
Reporter: Erik Stein | Owner: nobody
Type: Bug | Status: closed
Component: Core (URLs) | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by felixxm):
* status: new => closed
* version: 2.2 => master
* resolution: => invalid
Comment:
Thanks for the sample project. IMO everything works properly. In `DEBUG`
mode Django doesn't use your custom `404.html` page that's why it also
doesn't propagate any errors in this page (you've already described this
as a correct behavior). When `DEBUG=False` Django handles exception by
[https://docs.djangoproject.com/en/stable/ref/urls/#handler500 handler500]
view and logges them in
[https://docs.djangoproject.com/en/stable/topics/logging/#django-request-
logger django.request] logger. If you want to skip this and propagate
exceptions upwards when `DEBUG=False` you can use
[https://docs.djangoproject.com/en/2.2/ref/settings/#debug-propagate-
exceptions DEBUG_PROPAGATE_EXCEPTIONS] setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/30475#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bd283559ac66423d3012d176ce453b36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
