Replies: 1 comment
-
|
seriously agree,the revalidate is just the behavior in nextjs ssg,this should not effect deploys. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature you'd like to request
Today, a page generated with
getStaticPropsthat does not return therevalidatekey will send the cache control headers-maxage=31536000, stale-while-revalidate, which means that a CDN will cache the HTML across deploys, causing bugs. I would like to be able to say "The data behind this SSG page does not need to be updated between deploys" while also ensuring that the CDN does not cache my HTML.Describe the solution you'd like
Don't set
s-maxage=31536000, stale-while-revalidateifrevalidateis missing, only if it is actuallyfalse, or otherwise separate theCache-Controlheader from the datasource TTL.Describe alternatives you've considered
The workaround I am using now is to set
revalidate: 1, but that means that my data sources behind the SSG page are getting hit more than necessary.Beta Was this translation helpful? Give feedback.
All reactions