Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected Caching after Next.js 15 Upgrade #462

Closed
wei opened this issue Dec 19, 2024 · 0 comments · Fixed by #470
Closed

Unexpected Caching after Next.js 15 Upgrade #462

wei opened this issue Dec 19, 2024 · 0 comments · Fixed by #470
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@wei
Copy link
Owner

wei commented Dec 19, 2024

Steps to reproduce:

  1. I first went to https://socialify.git.ci after Next.js 15 upgrade ♻️ Full migration from app router PLUS next15/react19 #450 and saw the version number in the footer has been updated to v2.17.0 which is working as expected
  2. Subsequently, I deployed more new versions
  3. After refreshing the page, the footer is still showing the old 2.17.0 version where it should show 2.18.1.

I noticed the home page and possibly other pages now have these headers appended:

cache-control: s-maxage=31536000
x-nextjs-cache: HIT
x-nextjs-prerender: 1
x-nextjs-stale-time: 4294967294
image

For some additional context, our Socialify next.js server currently runs behind Cloudflare CDN. By specifying s-maxage=31536000, these pages are instructing CDN nodes like Cloudflare to cache the page for a year. I don't believe that's the desired behavior.

@KemingHe when you have a moment - could you help look into this issue and help us understand the root cause and make recommendations? TY!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
1 participant