From c590e9fef4f5977fe891cee4231251112a302fdc Mon Sep 17 00:00:00 2001 From: Doxa Maps Date: Fri, 2 Oct 2026 11:39:17 +0000 Subject: [PATCH] Gallery: after a deploy, a returning reader runs the new bundles, not stale cached copies A host that serves the tree with Last-Modified and no Cache-Control lets a browser run its cached files for hours. Measured: a typed-URL revisit after a deploy requested none of the gallery, the manifest or the bundles, so a returning reader ran the old files, or an old manifest against a new bundle. - The manifest is fetched with cache 'no-cache', so it is always revalidated (a 304 when unchanged). - A fingerprint of the manifest (every bundle's integrity) is kept per tree. When it differs from the reader's last visit, every bundle the browser already holds gets one conditional request before any tab mounts: a 304 refreshes it, and a 200 is cancelled at its headers, which drops the stale copy. The plain