#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:  new
    Component:  Core (URLs)  |                  Version:  2.2
     Severity:  Normal       |               Resolution:
     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 Erik Stein):

 * status:  closed => new
 * cc: Erik Stein (added)
 * resolution:  needsinfo =>


Old description:

> – 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]

New description:

 – 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.

 Sample project: https://github.com/sha-red/bugs-django-30475

--

Comment:

 I asked about adding a ticket for later reference before posting the issue
 and I would consider closing it after two days a bit unfortunate, but I
 don't really know your triaging policy, so please forgive me :-).

 Today I've added a simple sample project. In a first check it seems that
 the Django test client actually deals correctly with the buggy 404
 template (delivering a backtrace) making it somehow unuseful in testing
 the issue. I added some notes in the README instead.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30475#comment:3>
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/065.1e3b9c7694eafc9ddfb68ffe7a5bf2dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to