Should the revalidate route segment config option update the Cache-Control header?

[pauledwards241]

On one of our pages, we've added a dynamic route segment config and set it to:

export const dynamic = 'force-static';

This changes the page Cache-Control header to:

Cache-Control: public, max-age=0, must-revalidate

I then assumed adding a revalidate route segment config e.g.

export const revalidate = 600; // 10 minutes

Would update the Cache-Control header to:

Cache-Control: public, max-age=600, must-revalidate

But that's not the case. Based on this 2023 StackOverflow discussion, it should. However, it is 1.5 years old.

Is that expected? Does Next.js work out when to revalidate from other response headers instead?

We are hosting on Vercel if that makes a difference.