WEBVTT

00:00:00.000 --> 00:00:06.000
Changed a page but still see the old one?

00:00:06.000 --> 00:00:13.000
A saved copy may be part of the answer.

00:00:13.000 --> 00:00:18.000
Understand website caching.
6 useful points about saved copies.

00:00:18.000 --> 00:00:30.000
A cache stores a copy
Reusing a response can save another download.
Saved response · Fewer repeat requests · Faster repeat visits

00:00:30.000 --> 00:00:42.000
Copies can live in several places
Your browser and a delivery network may both cache files.
Browser cache · Shared cache · Website origin

00:00:42.000 --> 00:00:54.000
Freshness has a time limit
Cache rules tell services when a copy needs checking.
Fresh copy · Expiry time · Revalidation

00:00:54.000 --> 00:01:06.000
An update may need a purge
Ask your developer which shared cache needs refreshing.
Publish the change · Refresh shared copies · Check again

00:01:06.000 --> 00:01:18.000
Private pages need care
Personal responses must not be shared with other visitors.
Account pages · Personal information · Correct cache rules

00:01:18.000 --> 00:01:30.000
Compare a fresh visit
Test another browser before assuming the update failed.
New browser session · Correct page address · Confirm with your developer

00:01:30.000 --> 00:01:39.000
Your checklist
A cache stores a copy · Copies can live in several places · Freshness has a time limit · An update may need a purge · Private pages need care · Compare a fresh visit

00:01:39.000 --> 00:01:47.000
Check which copy your visitors receive.
jerseyweb.je