Keep the saved page, or fetch a new one?
One exchange at a time. Read what changes, then explain it in your own words before moving on.
- Meet the components
- Follow the steps
- Compare an example
- Check your understanding
Keep the saved page, or fetch a new one?
Example: a browser has yesterday’s timetable. A validator helps the server compare versions.
The browser validates its stored response and reuses the saved body.
How to use this example
Select Next step to read at your own pace, or Animate step to watch one exchange. Nothing advances until you choose.
What it means
Everyday example
State in this scenario
Inspect components & read every step
- Browser
The program you use to open websites.
Example: Your browser requests a web page and displays the response.
- Web server
Software that responds to requests for web content.
Example: It sends a page or confirms that a saved representation remains unchanged.
- Saved response
A previously stored web response that may be reused if caching rules allow it.
Example: The browser checks whether yesterday’s timetable is still current.
Page unchanged
The browser validates its stored response and reuses the saved body.
- Saved response Browser: Saved validator. The browser has a stored response with an ETag.
- Browser Web server: If-None-Match. A conditional GET asks whether this representation still matches.
- Web server Browser: 304 Not Modified. The server confirms a match without sending the full body.
Page changed
A different representation means the browser needs the new response body.
- Saved response Browser: Old validator. The browser has an earlier timetable response.
- Browser Web server: If-None-Match. The server compares the saved validator with the current version.
- Web server Browser: 200 + new body. The server sends the changed representation and relevant metadata.
Fictional teaching trace. One moving dot represents an exchange, not a measured network capture.