/explore
|
You are here 
|
httptoolkit.com | ||
| | | | |
techblog.thescore.com
Cache-Control directives are pretty straightforward to understand. They're easy to use as well if you assume that all the caches between your end user and application correctly implement the spec. Unfortunately, as with any spec, you can't make that assumption. |
|
| | | | | ||
| | | | |
www.integralist.co.uk
Introduction Caching is hard. Let's try and understand it a little better. Note: some sections are purposefully brief. I'm not aiming to be a specification document. Caching at multiple layers Caching can occur at both a 'client' level and a 'cache proxy' level. Consider the following request flow architecture diagram... In the above diagram, the "CDN" is a 'caching proxy' and so caching can (and of course does) happen there. |
|
| | | | | ||
| | | | |
www.mnot.net
The HTTP "core" documents were published on Monday, including a revision of HTTP semantics, caching, HTTP/1.1, HTTP/2, and the brand-new HTTP/3. However, that's not all that the HTTP community has been up to. |
|
| | | | | ||
| | | | |
eran.sandler.co.il
It's time to move my blog to version 3. This time we are going back in time and into the future at the same time. Before we begin, here is a little history of my blog: Version 1 - Blogger Version 1 ran on Blogger - which was essentially a static site generation platform. It gave you an editor, you would write your posts and then it would generate your complete site in HTML and even allowed you to publish it on your own server by uploading the result via FTP. |
|
| | | |||
