#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 Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Hi Erik.
Sorry for your irritation. I understand these things can be frustrating.
> I don't really know your triaging policy, so please forgive me :-).
See TicketClosingReasons/DontReopenTickets and The
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#triage-workflow Triage Workflow docs].
Ultimately here I think it's up to the user to ensure their 404 template
loads correctly. That's straight-forward to test. **If** they do introduce
an error, yes we drop right through to the very bottom
`handle_uncaught_exception()` but we know something bad has happened in
that case. As Mariusz points you to, `DEBUG_PROPAGATE_EXCEPTIONS` reveals
the issue immediately.
A custom 404 handler adding logging and/or exception handling around the
`get_template()` call would be possible. But it's unnecessary overhead: a
simple test that the 404.html template does in fact load makes this
unnecessary.
Sorry if that's not what you want to hear.
--
Ticket URL: <https://code.djangoproject.com/ticket/30475#comment:6>
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.1a97558227301aff0c42eaac7be5dac9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
