From f3901b5899d746dc5b754115d94ce9a045b4db0a Mon Sep 17 00:00:00 2001 From: David D Lowe Date: Sat, 7 Sep 2019 16:16:27 +0100 Subject: [PATCH] Doc'd that UpdateCacheMiddleware and cache_page affect downstream caches. Thanks to Nick Pope for review. --- docs/topics/cache.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index dcf47e65ca..f8e86ae85f 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -530,8 +530,9 @@ cached separately. This middleware expects that a HEAD request is answered with the same response headers as the corresponding GET request; in which case it can return a cached GET response for HEAD request. -Additionally, ``UpdateCacheMiddleware`` automatically sets a few headers in each -:class:`~django.http.HttpResponse`: +Additionally, ``UpdateCacheMiddleware`` automatically sets a few headers in +each :class:`~django.http.HttpResponse` which affect :ref:`downstream caches +`: * Sets the ``Expires`` header to the current date/time plus the defined :setting:`CACHE_MIDDLEWARE_SECONDS`. @@ -621,6 +622,10 @@ The ``key_prefix`` and ``cache`` arguments may be specified together. The ``key_prefix`` argument and the :setting:`KEY_PREFIX ` specified under :setting:`CACHES` will be concatenated. +Additionally, ``cache_page`` automatically sets ``Cache-Control`` and +``Expires`` headers in the response which affect :ref:`downstream caches +`. + .. versionchanged:: 3.1 In older versions, the ``max-age`` directive from the ``Cache-Control`` @@ -1109,6 +1114,8 @@ instance, to do this for the ``locmem`` backend, put this code in a module:: ...and use the dotted Python path to this class in the :setting:`BACKEND ` portion of your :setting:`CACHES` setting. +.. _downstream-caches: + Downstream caches =================