remoteEntry.js is cached -> this may cause the customization package to load incorrectly

[berndu]

Hi

I have encountered a situation on two occasions where an outdated remoteEntry.js was loaded in the browser and some of the chunks that remoteEntry was attempting to load no longer existed, as new chunks had been created due to changes to the customisation package.
The remoteEntry.js did not have a ‘no-cache’ header.
The chunks are versioned by name (the middle section of, for example, 310.329d668ce4aaae42.js), whereas remoteEntry is not. A solution is therefore required to ensure that an old version of remoteEntry.js is never served. As far as I can see, a no-cache header would be appropriate here.
Best
Bernd

[berndu]

I created SF case 10675469.

[DavidbdExl]

Fixed for september.