#13877: More documentation needed on exceptions in middlewares
-------------------------------------------------------+--------------------
Reporter: pakal <[email protected]> | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------------+--------------------
Changes (by pakal <[email protected]>):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
My tests show that if process_request, process_view or process_exception
raise an error, normal handling of this error occurs, depending on the
"DEBUG" setting : printing full stack information, or sending an email to
admins.
But if process_response raises an error, there is visibly no fallback
solution : the server simply outputs a raw traceback, and admins are not
notified of the error.
Shouldn't the exception management system protect "process_response" too,
so that admin notification and the display of a simple "error 500" page
occurs ?
--
Ticket URL: <http://code.djangoproject.com/ticket/13877#comment:1>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
