Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed note about ISP caching in docs. #14422

Merged
merged 1 commit into from May 20, 2021
Merged

Fixed note about ISP caching in docs. #14422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 7 additions & 5 deletions docs/topics/cache.txt
View file
Open in desktop
Expand Up @@ -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
Expand Down