Repository navigation
Bust browser caches when JavaScript or CSS changes - #292
Merged
Merged
Conversation
JavaScript and CSS are cached for a year, and the cache buster was the server version. A build with changed files but the same version, like a branch under test or a patched install, kept serving the old files to browsers that had them cached. The new HTML then ran against old JavaScript, which can break the page in ways that are hard to understand. The cache buster is now a hash of the JavaScript and CSS content, calculated when the server starts. Browsers get new files as soon as the content changes, and keep the long cache time when nothing changed. The version shown in the GUI stays the server version. Assisted-by: Claude Opus 5.5 noreply@anthropic.com
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
1 participant
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.
JavaScript and CSS are cached for a year, and the cache buster was the server version. A build with changed files but the same version, like a branch under test or a patched install, kept serving the old files to browsers that had them cached. The new HTML then ran against old JavaScript, which can break the page in ways that are hard to understand.
The cache buster is now a hash of the JavaScript and CSS content, calculated when the server starts. Browsers get new files as soon as the content changes, and keep the long cache time when nothing changed. The version shown in the GUI stays the server version.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com