Serve assets at content-hashed URLs with one-year cache TTL#288
Merged
Serve assets at content-hashed URLs with one-year cache TTL#288
Conversation
Computes a SHA256 hash of each asset file at startup and registers routes at the hashed URL (e.g. /assets/app-3f8a2c1b.css). The hash changes on every deploy, busting the browser cache automatically and allowing Cache-Control: public, max-age=31536000. No file copying or Dockerfile changes needed - the hashed URL simply points to the existing file on disk. Co-Authored-By: Claude Sonnet 4.6 <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.
Computes a SHA256 hash of each asset file at startup and registers routes at the hashed URL (e.g. /assets/app-3f8a2c1b.css). The hash changes on every deploy, busting the browser cache automatically and allowing Cache-Control: public, max-age=31536000. No file copying or Dockerfile changes needed - the hashed URL simply points to the existing file on disk.