From ff843bcbce1f7fc16fcc4d4810c221a2eb11c167 Mon Sep 17 00:00:00 2001 From: Zubair Hassan Date: Thu, 20 Nov 2025 16:38:47 +0500 Subject: Fixed #36734 -- Clarified the behavior of View.http_method_not_allowed. --- docs/ref/class-based-views/base.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/ref/class-based-views/base.txt b/docs/ref/class-based-views/base.txt index c1b302ea6a..887a83b37f 100644 --- a/docs/ref/class-based-views/base.txt +++ b/docs/ref/class-based-views/base.txt @@ -113,8 +113,9 @@ ancestor classes are documented under the section title of **Ancestors If the view was called with an HTTP method it doesn't support, this method is called instead. - The default implementation returns ``HttpResponseNotAllowed`` with a - list of allowed methods in plain text. + The default implementation returns ``HttpResponseNotAllowed`` with the + list of allowed methods in the ``Allow`` header, as required by + :rfc:`RFC 7231 <7231#section-6.5.5>`. The response body is empty. .. method:: options(request, *args, **kwargs) -- cgit v1.3