Django

Code

Ticket #760 (closed: wontfix)

Opened 3 years ago

Last modified 2 years ago

Error reason not seen when 500 template is missing

Reported by: wojtek@brandlay.com Assigned to: turkey
Milestone: Component: Admin interface
Version: Keywords:
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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.

Attachments

Change History

11/09/05 05:45:47 changed by rjwittams

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.

11/09/05 17:01:57 changed by adrian

rjwittams -- That solution sounds good.

11/21/05 19:17:35 changed by anonymous

  • status changed from new to closed.
  • resolution set to fixed.

11/25/05 10:21:10 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

11/25/05 10:21:20 changed by anonymous

  • status changed from reopened to closed.
  • resolution set to wontfix.

11/25/05 10:21:33 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

11/25/05 10:21:51 changed by anonymous

  • owner changed from adrian to turkey.
  • status changed from reopened to new.

11/25/05 11:38:14 changed by jacob

  • status changed from new to closed.
  • resolution set to fixed.

Hello Mr. Anonymous User!

This thing isn't a toy; please stop using it as one.

11/25/05 11:57:15 changed by hugo

  • status changed from closed to reopened.
  • resolution deleted.

Actually this ticket was open before Mr. Anonymous started to play, so maybe we should keep it open? ;-)

01/17/07 22:18:49 changed by SmileyChris

  • stage changed from Unreviewed to Accepted.

02/26/07 11:45:33 changed by jacob

  • status changed from reopened to closed.
  • resolution set to wontfix.

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.

Add/Change #760 (Error reason not seen when 500 template is missing)




Change Properties
Action