-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: set immutable cache-control for _next/static #2767
Merged
pieh
merged 2 commits into
main
from
michalpiechowiak/frb-1642-set-immutable-cache-control-headers-for-immutable-nextjs
Feb 21, 2025
Merged
fix: set immutable cache-control for _next/static #2767
pieh
merged 2 commits into
main
from
michalpiechowiak/frb-1642-set-immutable-cache-control-headers-for-immutable-nextjs
Feb 21, 2025
Conversation
This file contains 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
📊 Package size report 0.01%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
c9def8e
to
1626b6e
Compare
1626b6e
to
8ef6560
Compare
orinokai
approved these changes
Feb 21, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
We currently use default cache-control for
_next/static
which ispublic,max-age=0,must-revalidate
while it should bepublic,max-age=31536000,immutable
(per https://nextjs.org/docs/app/api-reference/config/next-config-js/headers#cache-control) as those assets have content hash in filename and therefore should be just permamently cached by browser without the need to revalidate with CDNDocumentation
Tests
Added global automatic fixture that ~passively assert
_next/static
responses cache-control headerRelevant links (GitHub issues, etc.) or a picture of cute animal
https://linear.app/netlify/issue/FRB-1642/set-immutable-cache-control-headers-for-immutable-nextjs-assets