From 75f107b8842dfc890ddd65262bd09ca87c3a15be Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Tue, 18 Nov 2014 11:57:05 -0500
Subject: Removed request.REQUEST per deprecation timeline; refs #18659.

---
 docs/topics/http/middleware.txt | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

(limited to 'docs/topics/http')

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
-- 
cgit v1.3