Code

Opened 8 years ago

Closed 7 years ago

#2322 closed defect (invalid)

Django FCGI interface doesn't display the 500 error page when an unhandled exception occurrs

Reported by: valery_z@… Owned by: adrian
Component: Core (Other) Version: master
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

If I set DEBUG = False in my settings.py, fcgi interface displayes a backtrace, which the user shouldn't see
(actually, flup does this, because WSGIServer is called without 'debug' parameter, and it is true by default).
I think there should be a command line option 'debug' in manage.py runfcgi.

Attachments (0)

Change History (2)

comment:1 Changed 8 years ago by ubernostrum

Could you clarify a bit more what you mean? I've deplyed Django under FCGI, and when I've broken it by accident my custom 500.html has been displayed in most cases; the only time it isn't is when an exception is raised in Django's own exception-handling code (which is difficult to do, but possible), in which case no amount of "debug" parameters can help -- an uncaught exception is always going to be an uncaught exception.

comment:2 Changed 7 years ago by Simon G. <dev@…>

  • Resolution set to invalid
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.