#31316: handler500 called multiple times.
-------------------------------+--------------------------------------
     Reporter:  David Szotten  |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  closed
    Component:  HTTP handling  |                  Version:  master
     Severity:  Normal         |               Resolution:  wontfix
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 This is made by design (see
 
[https://github.com/django/django/blob/daaa894960e1b2bce8ee31b7c109be84f598a84e/django/core/handlers/base.py#L140-L149
 process_exception_by_middleware()]), exceptions are processed by
 middlewares (see
 [https://docs.djangoproject.com/en/3.0/topics/http/middleware/#process-
 exception #process-exception]), and a default exception handler
 (`handler500`) is used when `process_exception()` is not implemented.
 That's why your custom (buggy) handler is used by all middlewares. Your
 implementation doesn't follow documentation and I don't think there is
 anything to change in Django.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31316#comment:4>
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.2d1060c4f8fb5de6801b25b2be50c99d%40djangoproject.com.

Reply via email to