Issue Bug Closed

#109711Unreliable asset caching in rolling-release deployments

Mathias Brodala 04/27/26, 07:51 updated 08/11/26, 08:46

Description

Given rolling-release deployments with multiple independent release directories and a symlink switch. The page output is cached with asset references of the current release.

However, switching to a new release does not affect the cached page output, instead a manual cache flush is necessary.

It would be useful if the page cache was invalidated automatically on release switch to ensure the page content is rendered and cached with the latest output including asset paths.

One solution would be to add the project path to the list of page cache identifier parameters.

Reviews 2

History 47

  1. Garvin Hicking commented and changed category <span data-processor="relativetime" data-value="2026-04-27T08:31:55+00:00" > 04/27/26, 08:31 </span>

    I wonder, usually also for rolling releases it’s best practice to flush and warmup caches, wouldn’t that obsolete the need for internal cache identifiers containing (and reading) that?

  2. Mathias Brodala commented <span data-processor="relativetime" data-value="2026-04-27T08:38:20+00:00" > 04/27/26, 08:38 </span>

    Garvin Hicking wrote in #note-2:
    > I wonder, usually also for rolling releases it’s best practice to flush and warmup caches, wouldn’t that obsolete the need for internal cache identifiers containing (and reading) that?

    Yes, we also do this and always did. However, for this particular case we saw errors in the frontend which were caused by the page content referring to obsolete asset paths (Webpack assets but loaded via f:asset.css / f:asset:script). Only after adding the project path to the cache identifier, the issue was gone.

  3. Mathias Brodala commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-05-02T17:00:10+00:00" > 05/02/26, 17:00 </span>

    Applied in changeset commit:57df1b21ce3254a5edd6710ed3bb65f226e569e3.