Set an explicit caching policy

[karifrederiksen]

Caddy has some default caching which leads to people having to force-clear their browser caches for every release.

Caching is fine for assets that include hashes in their names, such as the Javascript chunks. Caching images is probably fine for now since we never edit them - we can start hashing images once we start editing them.

index.html on the other hand can't be hashed since it is referred to by name in the Caddyfile, and since we can't add a hash to its name and it's the root of our application, we must disable caching for it. Maybe stale-while-revalidate is appropriate though.

[LinusPhoenix]

Let's try it first by adding the Cache-Control header in the Caddyfile for frontend requests, with the value max-age=259200, stale-while-revalidate.

[karifrederiksen]

Did you add the header? It's not in /frontend/caddy/Caddyfile on the dev branch.

[LinusPhoenix]

No, I did not

[LinusPhoenix]

I went ahead with setting Cache-Control response headers in Caddy with the following behavior:

• For files in /static/*, the cache never expires, the assets are marked immutable
• For files in /classes/*, /doges/*, /regions/*, /specs/*, and landing /landing/*, assets are fresh for a day, afterwards we have another period of using stale-while-revalidate for 6 days, to a total of 7 days caching time.

[LinusPhoenix]

Released in 1.0.0