Question about getServerSideProps caching behavior in Next.js

[software-based-boy]

Hi 👋

I’m experimenting with getServerSideProps and noticed that sometimes the data seems to be cached longer than I expected.
• Is there a built-in way to control or disable caching for getServerSideProps responses?
• Are there best practices to ensure fresh data on every request?

Thanks in advance for any guidance!

[sinavm]

[icyJoseph]

<sus> #85094

[sinavm]

This question is about the caching behavior of getServerSideProps in Next.js
Open your eyes 👀 #850127

[sinavm]

By default, getServerSideProps shouldn’t cache responses on the server each request should run the function anew. However, caching can happen at a few layers:
• CDN / edge caching: If you’re deploying on Vercel, the edge network might cache some responses unless you set proper headers.
• Browser caching: Make sure your response headers don’t allow client caching if you want fresh data every time.

If you want to enforce fresh data, you can set cache headers in your response, for example:

export async function getServerSideProps({ res }) {
  res.setHeader('Cache-Control', 'no-store');
  // fetch your data
  return { props: { /* data */ } };

}

This ensures that every request fetches fresh data and nothing is cached.