mirror of
https://github.com/django/django.git
synced 2025-08-03 18:38:50 +00:00
Fixed #26567 -- Updated references to obsolete RFC2616.
Didn't touch comments where it wasn't obvious that the code adhered to the newer standard.
This commit is contained in:
parent
fb68674ea4
commit
ac77c55bc5
13 changed files with 40 additions and 48 deletions
|
@ -321,8 +321,8 @@ Use the ``django.test.Client`` class to make requests.
|
|||
``Response`` object. Useful for simulating diagnostic probes.
|
||||
|
||||
Unlike the other request methods, ``data`` is not provided as a keyword
|
||||
parameter in order to comply with :rfc:`2616`, which mandates that
|
||||
TRACE requests should not have an entity-body.
|
||||
parameter in order to comply with :rfc:`7231#section-4.3.8`, which
|
||||
mandates that TRACE requests must not have a body.
|
||||
|
||||
The ``follow``, ``secure``, and ``extra`` arguments act the same as for
|
||||
:meth:`Client.get`.
|
||||
|
@ -484,8 +484,10 @@ Specifically, a ``Response`` object has the following attributes:
|
|||
|
||||
.. attribute:: status_code
|
||||
|
||||
The HTTP status of the response, as an integer. See
|
||||
:rfc:`2616#section-10` for a full list of HTTP status codes.
|
||||
The HTTP status of the response, as an integer. For a full list
|
||||
of defined codes, see the `IANA status code registry`_.
|
||||
|
||||
.. _IANA status code registry: https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml
|
||||
|
||||
.. attribute:: templates
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue