Default s-maxage=31536000 for static pages may cause stale content issues in CDN

[ale-grosselle]

Summary

Hi team 👋,

I've noticed that Next.js sets the following header for pages generated at build time: Cache-Control: s-maxage=31536000

While I understand the intention — treating these pages as fully static — this can lead to serious issues in production environments when served behind a CDN (such as Akamai, Cloudflare, etc.). Specifically:

• If a new build is deployed, the CDN may continue serving stale content for up to 1 year unless a manual purge is performed.
• CDNs won’t attempt revalidation (due to the long s-maxage), making it easy to overlook the issue.

I’m not sure I fully understand this choice — what am I missing or misunderstanding here?

Additional information

No response

Example

No response

[icyJoseph]

I'll try to investigate what's going on here

[l-you]

@icyJoseph Happens for me with the latest Umami (https://github.com/umami-software/umami) version on the dashboard page. They use Next.js.
Their /dashboard path is being white due to caching.