imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Old page after publishing: locate the cache layer

New CMS text does not prove the right version was built or delivered. Follow the same marked change from build artifact through origin, shared cache and browser.

Old page after publishing: locate the cache layer
  1. Starting condition

    New CMS text does not prove the right version was built or delivered. Follow the same marked change from build artifact through origin, shared cache and browser.

  2. Implementation

    Record URL, version and time. Confirm the change inside the built file and correct deployment environment before investigating caching. Compare delivered HTML and relevant headers through authorised access.

  3. Verification

    New build, old public response: compare origin and intermediate caches. New profile correct, old profile wrong: inspect local reuse and any service worker. A new query parameter is a separate case.

  4. Decision

    The same marked change appears in the build file and delivered page for the new and returning visits included in the test.

The same marked change appears in the build file and delivered page for the new and returning visits included in the test.

Which check determines the next step?

Correct the verified layer. Test ordinary loading and returning visits at the normal URL after the next publication. A successful purge does not prove a browser copy disappeared.

Start with a reproducible failure

Record URL, version and time. Confirm the change inside the built file and correct deployment environment before investigating caching. Compare delivered HTML and relevant headers through authorised access.

Use a small controlled test to separate a symptom from its cause. Record the starting state, affected URL and observed outcome so that another person can repeat the check.

A fictional website example

Fictional example: A course library changes a heading, but the build uses old source data. Purging cannot create text that was never built.

Collect evidence before changing anything

New build, old public response: compare origin and intermediate caches. New profile correct, old profile wrong: inspect local reuse and any service worker. A new query parameter is a separate case.

CheckExpected outcome
Starting conditionNew CMS text does not prove the right version was built or delivered. Follow the same marked change from build artifact through origin, shared cache and browser.
ImplementationRecord URL, version and time. Confirm the change inside the built file and correct deployment environment before investigating caching. Compare delivered HTML and relevant headers through authorised access.
VerificationThe same marked change appears in the build file and delivered page for the new and returning visits included in the test.

Fix the cause and repeat the test

Correct the verified layer. Test ordinary loading and returning visits at the normal URL after the next publication. A successful purge does not prove a browser copy disappeared.

Repeat the same test after the change and add a nearby case that already worked. One successful case establishes that task in those conditions; it does not certify the whole website.

Sources and further reading

Questions, answered

Is passing an automated test enough?

Combine technical checks with the actual visitor task. Document the environment, conditions and remaining limitations.

Which check determines the next step?

Correct the verified layer. Test ordinary loading and returning visits at the normal URL after the next publication. A successful purge does not prove a browser copy disappeared.

IMBAHUB

What would you like to make possible?

Describe the website task and the failure or development requirement you want to scope.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.