[szaimen]

Summary

Lazy-loaded chunks and their CSS are requested without the ?v= cache buster, so include the server version in their file names to make sure browsers and proxies never reuse them across updates.

Resolves a problem I got while upgrading my AIO-testing instance from Nc34.0.x to Nc35.0.2

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[szaimen]

/backport to stable35

[szaimen]

/backport to stable34

[susnux]

But its no problem to reuse the chunks you changed, because the hash is unique, there is no need to add any version or cache buster (thats the whole point of the hash).

What you like talk about are the entry points but those you cannot adjust with dynamic names, so for this we have our importmap in place which should already properly handle this - except your browser does not support importmaps.

[szaimen]

But its no problem to reuse the chunks you changed, because the hash is unique, there is no need to add any version or cache buster (thats the whole point of the hash).

In my case it was using outdate assets that were cached. It also pointed me here to the .htaccess file:

        <Else>
            Header set Cache-Control "max-age=15778463"
        </Else>

What you like talk about are the entry points but those you cannot adjust with dynamic names, so for this we have our importmap in place which should already properly handle this - except your browser does not support importmaps.

I am using the lates Chromium version, so pretty sure that that is not the problem.

[susnux]

In my case it was using outdate assets that were cached. It also pointed me here to the .htaccess file:

But you only changed the names of assets that are already named based on their content.
The assets you name here already have their hash in the name, so if they change the name changes as well.
Meaning those could not cause the problem you reported.