To start learning to love and understand caching, let's take a look at it's pieces.

Where to begin? Well what problem is caching trying to solve?

You might never think about it this way, but the idea of going to website is completely wrong. In reality, you are asking for the website to come to you.

And the problem that caching is trying to solve is when you ask for a website that has loads and loads of conent such as big pictures, videos, ads etc., how is all that going to be delievered quickly?

Before I go into caching I'd like to mention a few facts on requesting web pages with large amounts of content, just so we are on the same page.

And, caching is a feature built into the browser that helps manage these issues with pages that have loads of content.

The pieces that make up browser caching

Browser caching is a collection of Web API's that are found in all browsers.


Cache-Controls header allows you to control the cache on both the browser and server response. Along with the file, the server also sends instructions for how the file should be processed. In these instructions is where you would declare the Cache-Control header and a directive to it.


The ETag header controls the version of a resource and enables the cache to be more efficient and save bandwidth. By applying ETags to cached resources, the server can make requests better based on the tag, rather than scanning through the entire file again to see if it's the same or different.


Last-Modified is a record of the date the resource was last changed.

How this process works

When the user requests a web page, the request is first routed to the cache. To check if there are any of the resources already there. If the resources are in the cache, the page will use those resources and send fewer requests to the network.

Managing how the request routes to caching is controlled by messages attached to the request. These messages are called request headers and response headers. The request headers are the messages that deal with the browser asking for information. While the response headers are the messages that deal with sending information. The combination of these request/response headers serve as a way to configure and integrate cache is the information flow back n' forth between the browser and the server.

Request headers

As a developer, I don't have to touch these headers all that often from what I am gathering. The request headers are pre-configured and never really touched ever again. The request headers are made up of two messages If-None-Match and If-Modified-Since.

Response Headers

The response headers is where you as the developer set up the caching strategy for the page. The Cache-Control, ETag, and Last-Modified headers all belong here.

In the wild, you'll find that some web servers handle this aspect of caching for you, and others don't. Some web servers don't preconfigure the response headers because it's designed for the developer to integrate a custom caching strategy. If you need that level of control over caching and need to get very granular with caching, I would choose one of these web servers that leave your hands' caching strategy.

Configuring the Cache-Control, ETag, and Last-Modified in different ways is essentially how you develop a caching strategy. Here's a short video demonstrating how these work in the browser .