diff options
| author | Ben Sturmfels <ben@sturm.com.au> | 2021-05-20 10:17:16 +1000 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-05-20 11:24:26 +0200 |
| commit | a0782f50d49af7b0f00d33002c8fc2c248fea1bf (patch) | |
| tree | 7f13142aa1a7d08a820cb033c6dd44a06285e2d9 | |
| parent | d5c675ac7c06ef2d4a180ed5d2d83bdd539f4558 (diff) | |
[3.2.x] Fixed note about ISP caching in docs.
Regression in 7aabd6238028f4bb78d0687bbccc97bcf634e28b.
Backport of 31b6ce9ff938a0968f2e526f5d5e106fd17e3dfa from main
| -rw-r--r-- | docs/topics/cache.txt | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index cb254a71a7..a215886178 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -1144,11 +1144,13 @@ the request reaches your website. Here are a few examples of downstream caches: -* Your ISP may cache certain pages, so if you requested a page from - https://example.com/, your ISP would send you the page without having to - access example.com directly. The maintainers of example.com have no - knowledge of this caching; the ISP sits between example.com and your Web - browser, handling all of the caching transparently. +* When using HTTP, your :abbr:`ISP (Internet Service Provider)` may cache + certain pages, so if you requested a page from ``http://example.com/``, your + ISP would send you the page without having to access example.com directly. + The maintainers of example.com have no knowledge of this caching; the ISP + sits between example.com and your Web browser, handling all of the caching + transparently. Such caching is not possible under HTTPS as it would + constitute a man-in-the-middle attack. * Your Django website may sit behind a *proxy cache*, such as Squid Web Proxy Cache (http://www.squid-cache.org/), that caches pages for |