#30475: Use of i18n_patterns and a buggy 404 template trigger internal server
error
without a backtrace
---------------------------------------+------------------------
Reporter: sha-red | Owner: nobody
Type: Bug | Status: new
Component: Core (URLs) | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+------------------------
– Using i18n_patterns with prefix_default_language=True,
– trying to get the frontpage URL without a language given in the URL
works in debug mode, but gives an internal server error without any
backtrace in production mode.
This was caused by a buggy 404.html template, but probably buggy 404
templates should give a backtrace, too, and i18n_patterns shouldn't be
concerned by this anyway.
[draft bug report, I'll try to provide more details later or on request]
--
Ticket URL: <https://code.djangoproject.com/ticket/30475>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.3f38335c8b1e8f3cf2901d8c59bfc55c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.