From 6e8f42cfc7002dc8471baa9573da3e9b52006230 Mon Sep 17 00:00:00 2001 From: Kenneth Kam Date: Sun, 22 Feb 2015 17:46:15 +0000 Subject: [PATCH] [1.7.x] Fixed #23762 -- clarified CACHE_MIDDLEWARE_ANONYMOUS_ONLY deprecation in docs Backport of e83aba0e2cce16cd1b32d1c172239a4e20867e95 from master --- docs/releases/1.6.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 2c4ceef7e6..dc03d7a5a9 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -1042,10 +1042,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