#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 Tim Graham):
A discussion on the DevelopersMailingList would be needed to see if
there's consensus to make a backwards-incompatible change there. The
current behavior is
[https://docs.djangoproject.com/en/dev/topics/testing/tools/#exceptions
documented]. The commit that introduced that signal is
f9cdde0cb41851e9d1eb70bd108debb75f267585.
--
Ticket URL: <https://code.djangoproject.com/ticket/27760#comment:3>
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.6728eef5087ca136dbc66d050872dba8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
