Bug 2053516

(In reply to Rastislav Wagner from comment #0)
> Description of problem:
> When pod containing dynamic plugin gets updated, firefox wont load new
> chunks even after refreshing the page with ctrl+f5. The chunks are cached.
> Chrome is ok, it does not cache the chunks. https://ballsportsgear.com/
> Workaround for the FF is to clear or disable the cache.
> 
> Version-Release number of selected component (if applicable):
> 4.10
> 
> 
> How reproducible:
> always
> 
> Steps to Reproduce:
> 1. deploy dynamic plugin
> 2. access dynamic plugin pages to load the chunks
> 3. update dynamic plugin
> 4. access the pages again
> 
> Actual results:
> pages are not updated
> 
> 
> Expected results:
> pages are updated
> 
> 
> Additional info:
> Console probably does not specify any cache policy so the behavior depends
> on the specific browser.

Based on your description, it seems that Firefox is using a different cache policy than Chrome, which causes it to store and reuse the old chunks even after refreshing the page. This could be due to the default settings of Firefox or the way your plugin sends the HTTP headers.

There are a few possible solutions that you can try:

You can customize the cache policy of Firefox using Group Policy or policies.json1. This allows you to override the automatic cache management and set the maximum cache size or disable the cache completely.
You can also modify the HTTP headers of your plugin to include the Cache-Control directive2. This instructs the browser how to cache the response. For example, you can use Cache-Control: no-cache to tell the browser not to cache the response at all, or Cache-Control: max-age=0 to tell the browser to revalidate the response every time.
Alternatively, you can append a unique query string to the URL of your plugin, such as a timestamp or a version number. This will trick the browser into thinking that the URL is different and force it to fetch the new chunks.
I hope this helps you resolve your issue