fix(sim): bust HTTP cache on media preload so re-baked clips show #22

Merged
benstull merged 1 commits from fix/preload-cache-bust into main 2026-06-25 19:40:51 +00:00
Owner

The preload fetched each clip with the default HTTP cache, so a clip re-baked under the same path (e.g. the cosmos base re-sourced to the Webb Cosmic Cliffs flythrough) kept showing stale footage after a reload — worst case forever when a pre-no-cache build pinned it immutable, max-age=1y. Fetch the preload with cache: "reload" to bypass the HTTP cache and refresh the entry; the in-memory blob cache still gives instant in-session swaps.\n\n269 passed, 2 skipped.\n\n🤖 Generated with Claude Code

The preload fetched each clip with the default HTTP cache, so a clip re-baked under the same path (e.g. the cosmos base re-sourced to the Webb Cosmic Cliffs flythrough) kept showing stale footage after a reload — worst case forever when a pre-`no-cache` build pinned it `immutable, max-age=1y`. Fetch the preload with `cache: "reload"` to bypass the HTTP cache and refresh the entry; the in-memory blob cache still gives instant in-session swaps.\n\n269 passed, 2 skipped.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)
benstull added 1 commit 2026-06-25 19:40:48 +00:00
The preload fetched each clip with the default HTTP cache, so a clip re-baked
under the same path (e.g. the cosmos base re-sourced to the Webb Cosmic Cliffs
flythrough) kept showing stale footage after a reload — worst case forever, when
a pre-`no-cache` build had pinned it `immutable, max-age=1y` (a plain reload never
revalidates an immutable entry). Fetch the preload with `cache: "reload"`, which
bypasses the HTTP cache, pulls fresh bytes, and updates the cache entry; the
in-memory blob cache still gives instant in-session altitude swaps. One fetch per
(re)load, so no steady-state cost.

269 passed, 2 skipped. app.js syntax-checked.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
benstull merged commit aa56dfe145 into main 2026-06-25 19:40:51 +00:00
Sign in to join this conversation.