Add example of sane cache-control settings when hosting a vite SPA#512
Merged
mcollina merged 1 commit intofastify:mainfrom Mar 2, 2025
Merged
Add example of sane cache-control settings when hosting a vite SPA#512mcollina merged 1 commit intofastify:mainfrom
mcollina merged 1 commit intofastify:mainfrom
Conversation
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.
Adds a sane example of how one might setup the cache-control headers when using fastify-static to host a site, in particular a site built with vite.js
I've been burnt by this recently and I thought it could help others if it was front and center in the docs. In particular, looking at the existing examples, one might think that setting
cacheControl: falsewill disable caching when in fact it will simply disable setting the header and let the browser to it's default caching (which is rarely the desired outcome).related to #508 & #477
Not sure if this merits an example front in center in the readme, but it would have saved me some headache in some personal projects.
Checklist
npm run testandnpm run benchmarkand the Code of conduct