Documentation doesn't directly mention that BadRequest is handled by handler400

[Lincoln]

A BadRequest exception raised in a view, is handled by the handler400 view (default django.views.defaults.bad_request).

​https://github.com/django/django/blob/c68e4adea0703354508d51895b091771b1f6ac45/django/core/handlers/exception.py#L96-L104

Looking at the documentation, I can't see this link mentioned anywhere.

Places I looked:

• ​https://docs.djangoproject.com/en/dev/ref/views/#the-400-bad-request-view (This section only mentions SuspiciousOperation)
• ​https://docs.djangoproject.com/en/dev/topics/http/views/#customizing-error-views
• ​https://docs.djangoproject.com/en/dev/ref/urls/#handler400
• ​https://docs.djangoproject.com/en/dev/ref/exceptions/#badrequest

For comparison, This section about the 404 view

​https://docs.djangoproject.com/en/dev/ref/views/#the-404-page-not-found-view

explicitly says "When you raise Http404 from within a view, ..."

[Natalia Bidart]

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.

[Natalia Bidart]

Kundan, just a quick suggestion regarding ticket assignments: while you are getting started with Django contributions, it is usually best to focus on one ticket at a time and see it through fully, including reviews and any required follow-ups, before taking on additional tickets. This helps keep tickets moving and avoids unintentionally blocking other contributors. Thanks! and I appreciate the interest in contributing.

[Kundan Yadav]

i am sorry again i will keep all this in my mind am really sorry again

[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.

[Lincoln]

I am happy to provide a PR, since I am the one complaining

[Natalia Bidart]

Replying to Lincoln:

I am happy to provide a PR, since I am the one complaining

Amazing, thank you Lincoln! I'll switch ownership to you, following my conversation with Kundan.