fix: Avoid caching of config file

[frankkopp]

Summary of Changes

As it sometimes takes forever for users to see new configs we should make sure the config file is not cached.

I tried with a http header which didn't work. So added a cache-killer parameter.

Additional context

https://discord.com/channels/738864299392630914/846470774361161808/1307387181605847120

Discord username (if different from GitHub): cdr_maverick

[Revyn112]

@frankkopp How you've tried to set the header?
Just wondering, as we are using the cache control within the fetch options and have no problems with cached configuration files so far.

return await fetch(url, { cache: "no-store" })

https://github.com/headwindsim/installer/blob/a2087477e5391dd2c33b90d453e3ef95fda31d1f/src/renderer/utils/InstallerConfiguration.ts#L406

[pdellaert]

If the cache: "no-store" works, I'd prefer that, as it is a cleaner approach. But not sure how aggressive Cloudflare caching can be.

[frankkopp]

@frankkopp How you've tried to set the header?

Just wondering, as we are using the cache control within the fetch options and have no problems with cached configuration files so far.

return await fetch(url, { cache: "no-store" })

https://github.com/headwindsim/installer/blob/a2087477e5391dd2c33b90d453e3ef95fda31d1f/src/renderer/utils/InstallerConfiguration.ts#L406

Can try that. But I'm rather sure it had this in it as well.

[FoxtrotSierra6829]

If the cache: "no-store" works, I'd prefer that, as it is a cleaner approach. But not sure how aggressive Cloudflare caching can be.

The issue is not about the caching in Cloudflare's CDN, but the Installer's dynamic Chromium disk cache.

[frankkopp]

I tested a few more headers - but I think they do not influence the internal cache of the Chromium cache.
Only the cache-killer seem to work.

return await fetch(url, { cache: 'no-store' })

or these:

return await fetch(url, { headers: { 'Cache-Control': 'no-store, no-cache, must-revalidate, max-age=0, private' } })

The server (CloudFlare) seems to also override these headers in its response:

So - it seems only the cache-killer param works.

[pdellaert]

In that case, cache-killer is the way forward :). Thanks for all the testing!