Opened 18 years ago
Closed 18 years ago
#2322 closed defect (invalid)
Django FCGI interface doesn't display the 500 error page when an unhandled exception occurrs
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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.
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.htmlhas 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.