mirror of
https://github.com/django/django.git
synced 2025-11-17 10:43:25 +00:00
[Docs] Clarify behavior of View.http_method_not_allowed default implementation
This commit is contained in:
parent
5c60763561
commit
3ca6c60636
1 changed files with 8 additions and 2 deletions
|
|
@ -113,8 +113,14 @@ 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
|
||||
status code ``405 Method Not Allowed``.
|
||||
|
||||
.. note::
|
||||
|
||||
Django sets the list of allowed HTTP methods in the ``Allow``
|
||||
response header, and the response content is empty.
|
||||
|
||||
|
||||
.. method:: options(request, *args, **kwargs)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue