p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #22827 -- clarified what each cache middleware does. 

Thanks Keryn Knight for the report.
This commit is contained in:
Moayad Mardini 2014-07-25 11:42:06 +03:00 committed by Tim Graham
parent aa8bc7fa7d
commit f9b7a0383c
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/topics/cache.txt
View File

@ -465,14 +465,14 @@ Then, add the following required settings to your Django settings file:
the site, or some other string that is unique to this Django instance, to
prevent key collisions. Use an empty string if you don't care.
The cache middleware caches GET and HEAD responses with status 200, where the request
and response headers allow. Responses to requests for the same URL with different
query parameters are considered to be unique pages and are cached separately.
The cache 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.
``FetchFromCacheMiddleware`` caches GET and HEAD responses with status 200,
where the request and response headers allow. Responses to requests for the same
URL with different query parameters are considered to be unique pages and are
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, the cache middleware automatically sets a few headers in each
Additionally, ``UpdateCacheMiddleware`` automatically sets a few headers in each
:class:`~django.http.HttpResponse`:
* Sets the ``Last-Modified`` header to the current date/time when a fresh