mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Removed settings.CACHE_MIDDLEWARE_ANONYMOUS_ONLY per deprecation timeline.
refs #15201.
This commit is contained in:
parent
8b81dee60c
commit
f567d04b24
3 changed files with 5 additions and 105 deletions
|
@ -279,26 +279,6 @@ Default: ``default``
|
|||
|
||||
The cache connection to use for the cache middleware.
|
||||
|
||||
.. setting:: CACHE_MIDDLEWARE_ANONYMOUS_ONLY
|
||||
|
||||
CACHE_MIDDLEWARE_ANONYMOUS_ONLY
|
||||
-------------------------------
|
||||
|
||||
Default: ``False``
|
||||
|
||||
.. deprecated:: 1.6
|
||||
|
||||
This setting was largely ineffective because of using cookies for sessions
|
||||
and CSRF. See the :doc:`Django 1.6 release notes</releases/1.6>` for more
|
||||
information.
|
||||
|
||||
If the value of this setting is ``True``, only anonymous requests (i.e., not
|
||||
those made by a logged-in user) will be cached. Otherwise, the middleware
|
||||
caches every page that doesn't have GET or POST parameters.
|
||||
|
||||
If you set the value of this setting to ``True``, you should make sure you've
|
||||
activated ``AuthenticationMiddleware``.
|
||||
|
||||
.. setting:: CACHE_MIDDLEWARE_KEY_PREFIX
|
||||
|
||||
CACHE_MIDDLEWARE_KEY_PREFIX
|
||||
|
@ -2885,7 +2865,6 @@ Cache
|
|||
-----
|
||||
* :setting:`CACHES`
|
||||
* :setting:`CACHE_MIDDLEWARE_ALIAS`
|
||||
* :setting:`CACHE_MIDDLEWARE_ANONYMOUS_ONLY`
|
||||
* :setting:`CACHE_MIDDLEWARE_KEY_PREFIX`
|
||||
* :setting:`CACHE_MIDDLEWARE_SECONDS`
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue