#19866: SuspiciousOperation should not be answered with HTTP 500
---------------------------------+------------------------------------
Reporter: tiwoc | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by digimag@…):
Quick idea: the 500 error could still be raised if the allowed hosts list
is empty (because it is clearly a misconfiguration). But if the list is
not empty, there is no reason why admins should be notified by e-mail. You
can throw a more appropriate response (403 or 400 error page) and if you
really want it, you can simply log this event.
What do you think about it?
--
Ticket URL: <https://code.djangoproject.com/ticket/19866#comment:14>
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 post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
