#36848: Documentation doesn't directly mention that BadRequest is handled by
handler400
-------------------------------------+-------------------------------------
Reporter: Lincoln | Owner: Kundan
Type: | Yadav
Cleanup/optimization | Status: assigned
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: handler400 | Triage Stage: Accepted
bad_request |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Lincoln):
Thanks Natalia for the quick reply.
To me (someone not familiar with Django internals) its not obvious what
the part about "reaches the ASGI/WSGI handler level" in `BadRequest` docs
means.
The part "results in a `HttpResponseBadRequest`." is ambiguous to me, that
could be a 400 response with no body.
The `handler400` docs say "the view that should be called if the HTTP
client has sent a request that caused an error condition and a response
with a status code of 400."
This is also ambiguous to me. For example a view that manually returns a
400 response, does NOT trigger this handler, when you could interpret it
to mean that.
--
Ticket URL: <https://code.djangoproject.com/ticket/36848#comment:6>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b9c403608-77a49a25-ef2b-4083-8acb-f25346ba72a0-000000%40eu-central-1.amazonses.com.
