#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 | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
Since #26666 was fixed, requests made with the test client that set
`SERVER_NAME` will return a 400, where the body of the response is simply
"<h1>Bad Request (400)</h1>".
To work out what's gone wrong, you have to grep the Django source code for
`Bad Request`. Could there be a better way to communicate the cause of
the problem?
--
Ticket URL: <https://code.djangoproject.com/ticket/27760>
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/050.f78c91730e7e4eb53c352cdfd0eb70b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
