Repository navigation
Revalidate the dashboard's files at each load - #103
Merged
Merged
Conversation
They were served with ETag and Last-Modified but no Cache-Control, so browsers reused cached copies and kept running the old dashboard after an upgrade. Cache-Control: no-cache makes them ask each time (304 when unchanged). Fixes #102
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #102
The dashboard's static files had an ETag and Last-Modified but no
Cache-Control, so browsers reused their cachedapp.js/style.cssheuristically: after an upgrade, the old dashboard kept running until a hard refresh. Now served withCache-Control: no-cache(revalidated each load, a 304 when unchanged). Test included.🤖 Generated with Claude Code