From cb33e553ee537da4915f9055f8cdf9bf32113aed Mon Sep 17 00:00:00 2001 From: Vasiliy Faronov Date: Mon, 2 May 2016 15:35:05 +0300 Subject: [1.9.x] Fixed #26567 -- Updated references to obsolete RFC2616. Didn't touch comments where it wasn't obvious that the code adhered to the newer standard. Backport of ac77c55bc5fc54cd763a7ae426784650a8cc97c9 from master --- docs/ref/models/querysets.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'docs/ref/models') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index b215cae761..92dbe803b6 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1733,9 +1733,7 @@ Finally, a word on using ``get_or_create()`` in Django views. Please make sure to use it only in ``POST`` requests unless you have a good reason not to. ``GET`` requests shouldn't have any effect on data. Instead, use ``POST`` whenever a request to a page has a side effect on your data. For more, see -`Safe methods`_ in the HTTP spec. - -.. _Safe methods: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1.1 +:rfc:`Safe methods <7231#section-4.2.1>` in the HTTP spec. .. warning:: -- cgit v1.3