#31316: handler500 called multiple times.
-------------------------------+--------------------------------------
Reporter: David Szotten | Owner: nobody
Type: Uncategorized | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by David Szotten):
apologies if i was being unclear. i acknowledge that the root cause was a
bug in my 500 handler "(poorly designed)". however, my question was about
how django should behave in the presence of such bugs. bugs are a fact of
life, and for when they happen in regular view code, django provides the
handler500 hook for custom error pages. it doesn't seem unreasonable that
from time to time we also have bugs in our error handlers, and my question
is how we want django to behave then. is the current behaviour of re-
calling the handler500 once for each middleware desired in this case, or
would we be interested in exploring other options? (or, perhaps it's not
ideal but too rare to bother improving)
--
Ticket URL: <https://code.djangoproject.com/ticket/31316#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.4bfe82149417f8eb407144205fdb8a24%40djangoproject.com.
