Nextjs cache and cloudflare cache are not synced with getStaticProps revalidation

Question

I’m trying to test my nextjs application on digital ocean, I deployed it, and noticed that getStaticProps revalidation doesn’t work, I examined the cache headers and notice that the revalidation paramater is being asssigned to Cache-Control like follow:

Cache-Control: s-maxage=10800, stale-while-revalidate

Which is what I am for, to tell nextjs to regenerate the page every 3 hours to update data. But the issue is, nextjs and cloudflare are not synced. So now the status is:

Cf-Cache-Status: HIT
X-Nextjs-Cache: STALE

Which means that for nextjs the page is expired, but for CF it’s not, so while nextjs might regenerate the page in the background it won’t show the new page until cloudflare cache will also expire.

Is there a way to fix it and sync them? Currently the application doesn’t have domain, so it’s all managed by digitalocean, but I am not sure if it's digitalocean issue or next ~ cloudflare issue that I can fix by configuration on either side.

Agustin Moles · Accepted Answer · 2024-05-22 13:13:48Z

0

NextJS does not support Static Regeneration with the Edge Runtime thus next-on-pages neither, you might want to check this documentation: https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/docs/supported.md#rendering-and-data-fetching

A fix would be to change to getServerSideProps if you are using pages router

answered May 22, 2024 at 13:13

Agustin Moles

1,5649 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Nextjs cache and cloudflare cache are not synced with getStaticProps revalidation

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related