summaryrefslogtreecommitdiff
path: root/docs/topics/testing
diff options
context:
space:
mode:
authorVasiliy Faronov <vfaronov@gmail.com>2016-05-02 15:35:05 +0300
committerTim Graham <timograham@gmail.com>2016-05-03 11:14:40 -0400
commitac77c55bc5fc54cd763a7ae426784650a8cc97c9 (patch)
treeaaf79c0eebbbad7d15c26f308de7ec47d1a81405 /docs/topics/testing
parentfb68674ea4b05280e3deb2ed23602038755092bc (diff)
Fixed #26567 -- Updated references to obsolete RFC2616.
Didn't touch comments where it wasn't obvious that the code adhered to the newer standard.
Diffstat (limited to 'docs/topics/testing')
-rw-r--r--docs/topics/testing/tools.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 722debcc91..042608efbd 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -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