BacLuc / ecamp3 / 27785458250

36%

devel: 36%

push

github

fix(frontend): set cache-control headers to avoid stale index.html

The nginx serving the built frontend did not emit any Cache-Control
headers, so browsers applied heuristic caching. A stale cached
index.html keeps referencing content-hashed assets that no longer
exist after a deployment, producing console errors and broken
functionality (issue #7633).

Serve the content-hashed files under /assets/ as immutable so they can
be cached indefinitely, and force revalidation of the entry point
(index.html, including SPA-route fallbacks) and the runtime config
environment.js via Cache-Control: no-cache. Revalidation stays cheap
thanks to the existing ETag (304). Also return a real 404 for missing
assets instead of silently falling back to index.html.

Fixes #7633

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: BacLuc <lucius.bachmann@clubpage.ch>

840 of 4746 branches covered (17.7%)

Branch coverage included in aggregate %.

4856 of 11182 relevant lines covered (43.43%)

983.78 hits per line