Opened 19 years ago
Closed 18 years ago
#760 closed defect (wontfix)
Error reason not seen when 500 template is missing
Reported by: | Owned by: | turkey | |
---|---|---|---|
Component: | contrib.admin | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When DEBUG = False (production environment) and an error happens, and the 500 template is not provided - one gets a traceback about the template not existing, but does not get a traceback for the exception that caused the actual failure.
Change History (11)
comment:1 by , 19 years ago
comment:3 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 19 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:5 by , 19 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
comment:6 by , 19 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
comment:7 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
comment:8 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Hello Mr. Anonymous User!
This thing isn't a toy; please stop using it as one.
comment:9 by , 19 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Actually this ticket was open before Mr. Anonymous started to play, so maybe we should keep it open? ;-)
comment:10 by , 18 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:11 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Django's not going to ever include a default 404 or 500 template. If we do, people won't be forced to create their own, and an error will quickly reveal what software your server's running (think "Application Error (Rails)").
However, [4612] adds a comment to the line that will fail so that at least people will get a slightly better idea of where to go next.
I don't think that by default with errors off we should reveal internal implementation details.
One solution for this error template situation would be "last chance" template loader. This would just respond to the 400, 500, and template_debug template names, and would be last in the list of loaders ( maybe appended automatically to this list). It would load extremely simple templates from strings, meaning it only relies on python module loading.