innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed note about ISP caching in docs. 

Regression in 7aabd62380.
This commit is contained in:
Ben Sturmfels 2021-05-20 10:17:16 +10:00 committed by Mariusz Felisiak
parent 736bb9868a
commit 31b6ce9ff9
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/topics/cache.txt
View File

@ -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