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 10:55:42 +0200 |
| commit | 31b6ce9ff938a0968f2e526f5d5e106fd17e3dfa (patch) | |
| tree | 8a0ff0fd5497b047d870afb24a7c2b0f6c0543e3 /docs | |
| parent | 736bb9868a1299f7613adbe2e71583777aa5403e (diff) | |
Fixed note about ISP caching in docs.
Regression in 7aabd6238028f4bb78d0687bbccc97bcf634e28b.
Diffstat (limited to 'docs')
| -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 6ae1e1e376..4c0dbd83f5 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -1135,11 +1135,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 |