#28693: DisallowedHost can cause uncaught exception and HTTP 500
--------------------------------+------------------------------------------
Reporter: Greg Price | Owner: Tomer Chachamu
Type: Bug | Status: assigned
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution:
Keywords: DisallowedHost | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------------
Changes (by Tomer Chachamu):
* owner: nobody => Tomer Chachamu
* status: new => assigned
* stage: Unreviewed => Accepted
Comment:
There would need to be a deprecation path for custom 400 views that are
using csrf tokens, so I think catching DisallowedHost in the traceback is
the right answer here.
--
Ticket URL: <https://code.djangoproject.com/ticket/28693#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.0de1c95edb60e27ad5ab26ff6e0b730f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
