Fixed #23762 -- clarified CACHE_MIDDLEWARE_ANONYMOUS_ONLY deprecation in docs

2 files changed, 9 insertions, 5 deletions

diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt
index 01a11d9a96..e155d5873e 100644
--- a/docs/releases/1.6.txt
+++ b/docs/releases/1.6.txt
@@ -1040,10 +1040,11 @@ If necessary, you can temporarily disable auto-escaping with
 ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-``CacheMiddleware`` used to provide a way to cache requests only if they
-weren't made by a logged-in user. This mechanism was largely ineffective
-because the middleware correctly takes into account the ``Vary: Cookie`` HTTP
-header, and this header is being set on a variety of occasions, such as:
+``CacheMiddleware`` and ``UpdateCacheMiddleware`` used to provide a way to
+cache requests only if they weren't made by a logged-in user. This mechanism
+was largely ineffective because the middleware correctly takes into account the
+``Vary: Cookie`` HTTP header, and this header is being set on a variety of
+occasions, such as:
 
 * accessing the session, or
 * using CSRF protection, which is turned on by default, or
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index 6a3b5554a6..1820039bf9 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -1723,7 +1723,10 @@ removed in Django 1.8 (please see the :ref:`deprecation timeline
 
 * The module ``django.test._doctest`` is removed.
 
-* The ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting is removed.
+* The ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting is removed. This change
+  affects both ``django.middleware.cache.CacheMiddleware`` and
+  ``django.middleware.cache.UpdateCacheMiddleware`` despite the lack of a
+  deprecation warning in the latter class.
 
 * Usage of the hard-coded *Hold down "Control", or "Command" on a Mac, to select
   more than one.* string to override or append to user-provided ``help_text`` in