#27760: Hard to diagnose reason for 400 response when making test request that
sets
SERVER_NAME
-----------------------------------+--------------------------------------
Reporter: Peter Inglesby | Owner: nobody
Type: Uncategorized | Status: new
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
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 Peter Inglesby):
Running the test with `--debug-mode` does tell you what the problem is,
but it's only useful if you know that it exists, and even then it's not
obvious that it would help.
I've been poking around core/handlers/exception.py, and was able to get
the behaviour I'm after by adding
`signals.got_request_exception.send(sender=None, request=request)` to the
`SuspiciousOperation` branch of `response_for_exception`. Would this be a
viable approach?
--
Ticket URL: <https://code.djangoproject.com/ticket/27760#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 [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.27ccf1db8c92507812dd33125cc7cb71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
