#36848: Documentation doesn't 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
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* keywords: => handler400 bad_request
* stage: Unreviewed => Accepted
* version: => dev
Comment:
Hello Lincoln! Thanks for the report.
While the current documentation already describes this behavior indirectly
(the `BadRequest` exception docs says they resul in an
`HttpResponseBadRequest` at the handler level with a status code of 400,
and `handler400` being responsible for rendering 400 responses), I agree
that an explicit mention similar to `Http404` would improve clarity.
Accepting this as a small documentation clarification.
--
Ticket URL: <https://code.djangoproject.com/ticket/36848#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b9888e86c-fb771e91-0a85-496b-96d6-802773a915c7-000000%40eu-central-1.amazonses.com.
