summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2014-11-18 11:57:05 -0500
committerTim Graham <timograham@gmail.com>2015-01-17 08:05:18 -0500
commit75f107b8842dfc890ddd65262bd09ca87c3a15be (patch)
treea1e30fc3d82e3a1f281caccd078108daea93c7b5 /docs
parent61ad1ea92b1f4df992b0ef1dcc7c781da2413815 (diff)
Removed request.REQUEST per deprecation timeline; refs #18659.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/request-response.txt15
-rw-r--r--docs/topics/http/middleware.txt11
2 files changed, 5 insertions, 21 deletions
diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt
index 1375ba10e5..41e6d3dcdc 100644
--- a/docs/ref/request-response.txt
+++ b/docs/ref/request-response.txt
@@ -108,21 +108,6 @@ All attributes should be considered read-only, unless stated otherwise below.
Note: ``POST`` does *not* include file-upload information. See ``FILES``.
-.. attribute:: HttpRequest.REQUEST
-
- .. deprecated:: 1.7
- Use the more explicit ``GET`` and ``POST`` instead.
-
- For convenience, a dictionary-like object that searches ``POST`` first,
- then ``GET``. Inspired by PHP's ``$_REQUEST``.
-
- For example, if ``GET = {"name": "john"}`` and ``POST = {"age": '34'}``,
- ``REQUEST["name"]`` would be ``"john"``, and ``REQUEST["age"]`` would be
- ``"34"``.
-
- It's strongly suggested that you use ``GET`` and ``POST`` instead of
- ``REQUEST``, because the former are more explicit.
-
.. attribute:: HttpRequest.COOKIES
A standard Python dictionary containing all cookies. Keys and values are
diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt
index cc7607da0a..7e1e01dd87 100644
--- a/docs/topics/http/middleware.txt
+++ b/docs/topics/http/middleware.txt
@@ -130,12 +130,11 @@ view; it'll apply response middleware to that
.. note::
- Accessing :attr:`request.POST <django.http.HttpRequest.POST>` or
- :attr:`request.REQUEST <django.http.HttpRequest.REQUEST>` inside middleware
- from ``process_request`` or ``process_view`` will prevent any view running
- after the middleware from being able to :ref:`modify the upload handlers
- for the request <modifying_upload_handlers_on_the_fly>`, and should
- normally be avoided.
+ Accessing :attr:`request.POST <django.http.HttpRequest.POST>` inside
+ middleware from ``process_request`` or ``process_view`` will prevent any
+ view running after the middleware from being able to :ref:`modify the
+ upload handlers for the request <modifying_upload_handlers_on_the_fly>`,
+ and should normally be avoided.
The :class:`~django.middleware.csrf.CsrfViewMiddleware` class can be
considered an exception, as it provides the