Set default stale-while-revalidate header value to 1 year #65867
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.
This follows 2 previous PRs, #52251 and #61330 by making a 1 year expiry the default for the
stale-while-revalidate
header.As far as I can tell, the current default is invalid according to RFC 5861.
Any user deploying Next.js behind any CDN other Vercel expects SWR to work correctly, but it does not because there is no default expiry value.
This change will make the default work for all Next.js users and greatly reduce frustration for those of us deploying Next.js places besides Vercel.
This also fixes a small edge case where
experimental.swrDelta = 0
would not function as expected.Thank you!