HTTP caching - HTTP | MDN
developer.mozilla.org · 5,238 words · saved by 1 readers
The HTTP cache stores a response associated with a request and reuses the stored response for subsequent requests.
HTTP caching - HTTP | MDN Skip to main content Skip to search HTTP caching The HTTP cache stores a response associated with a request and reuses the stored response for subsequent requests. There are several advantages to reusability. First, since there is no need to deliver the request to the origin server, then the closer the client and cache are, the faster the response will be. The most typical example is when the browser itself stores a cache for browser requests. Also, when a response is reusable, the origin server does not need to process the request — so it does not need to parse and r
related reading
- RFC 9111 - HTTP Cachinghttpwg.org
- A very concrete explanation of how a cache worksparksb.github.io
- Getting Started: Caching | Next.jsnextjs.org
- Using HTTP cookies - HTTP | MDNdeveloper.mozilla.org
- workbox-precaching | Modules | Chrome for Developersdeveloper.chrome.com
- Populating the page: how browsers work - Performance | MDNdeveloper.mozilla.org
- Cache strategies · Hugging Facehuggingface.co
- help.zscaler.comhelp.zscaler.com
- What is Memoization? How and When to Memoize in JavaScript and Reactfreecodecamp.org
- CDN Vs Edge Server | How Does Edge Caching Work?belugacdn.com
- CDNs aren't just for cachingjvns.ca
- What is a CDN? - Content Delivery Network Explained - AWSaws.amazon.com