#33981: When a DisallowedHost exception is raised, the log message contains an
exception trace
-------------------------------------+-------------------------------------
Reporter: Andrew Selby | Owner: (none)
Type: Uncategorized | Status: closed
Component: Error reporting | Version: 4.1
Severity: Normal | Resolution: wontfix
Keywords: DisallowedHost | Triage Stage:
HTTP_HOST exception trace | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi Andy.
I think removing the traceback would be a net-negative. I want to see a
traceback when an exception is logged.
I also think that the previous PR was implemented as intended by the
author, and the three reviewers.
Hence triaging as wontfix.
The appropriate route forward if you want the ticket reopened is to post
the DevelopersMailingList as per
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#closing-tickets the ticket triage guidelines for closed tickets].
If there is a consensus for re-opening there then we can reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/33981#comment:7>
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/0107018312eb1edb-7f50c812-b25b-4b06-a50f-19488ca098dd-000000%40eu-central-1.amazonses.com.
