Make reuse and updates part of the same delivery decision.
ImbaHub can implement a bounded cache policy for public website content. We connect resource classes, publishing requirements and repeatable tests so that a fast response also contains the version visitors need.
- Classify
Define public status, change pattern and address model.
- Configure
Connect decisions to real delivery layers.
- Verify
Test updates and rollback for first and returning visits.
Decide cache lifetime and publishing requirements together.
The CDN is purged but a returning visitor sees old HTML. All layers verified?
No. Investigate browser reuse and other actual layers without assuming the purge reached them.
Classify resources before choosing lifetimes
Inventory public HTML, versioned styles and scripts, images and any user-dependent responses. Decide which content changes at the same URL and which receives a new address. One rule for everything can produce unnecessary requests or stale pages.
A fictional training provider updates course information at a stable address while built stylesheets have versioned names. Those resources need not share a policy. Private previews and customer content require a separate assessment.
Connect the policy to actual cache layers
Review the origin, any CDN and browser caching. Include service-worker behavior if the site has it. A response header in source code does not establish what every layer delivers.
no-cache can allow storage while requiring validation before reuse; no-store serves a different purpose. Document the host’s interpretation and overrides instead of choosing directives by name alone.
| Resource | Decision | Acceptance check |
|---|---|---|
| Public HTML | When updates must be checked | Delivered text meets publishing needs |
| Versioned asset | New address when bytes change | HTML references a working intended file |
| Stable image URL | How replacement becomes visible | Returning visit receives tested outcome |
| Private response | Permitted storage and sharing | No accidental public rule |
| Removed page | Expiry and invalidation | Old content is not mistaken for active content |
Test updates and rollback
Publish a marked change in a safe environment. Compare first and returning visits, actual headers, version and dependent files. Also test returning to the previous working release.
A CDN purge does not automatically remove browser copies. New response directives cannot be assumed to reach a fresh stored copy that makes no request. Design the update route before selecting long lifetimes.
Hand over clear operational responsibility
An initial scope can cover selected public page types and one hosting environment. Delivery includes configuration, resource register, tests and rollback. Authenticated content and offline features are scoped explicitly.
Pricing follows review of access and provider behavior. Real operational changes require agreed scope. We promise neither a universal cache duration nor immediate withdrawal of all stored copies from every device.
Sources and further reading
Questions, answered
Can every file use the same lifetime?
It depends on change patterns, privacy and delivery requirements. Stable HTML and versioned files commonly need different decisions.
Does a CDN purge clear a visitor’s browser?
Not automatically. Shared caches and stored browser responses are separate layers.