setting Cache-Control header in getServerSideProps on generated JSON is not working on production

[dulmandakh]

Bug report

Thank you for Next.js and it's 9.3 version, it's amazing.

Describe the bug

I'm trying to set reasonable Cache-Control header in getServerSideProps for generated JSON file, then it works on dev server but not on production builds or set to no-cache, no-store, must-revalidate.

But Cache-Control works as expected when you visit the link directly or for generated html.

I'm running my own server.

To Reproduce

1. Create pages/about.js file with content like below

export async function getServerSideProps({ res }) {
  res.setHeader('Cache-Control', 'public, max-age=7200')
  return {
    props: {
    }
  };
}

export default function() {
  return <h1>About</h1>
}

2. Create a like to about page using code below

<Link href="/about"><a href="/about">About</a></Link>

3. Start dev server and open any page other than about, then navigate to about page. Then you will see about.json in a browser inspector and it's Cache-Control header set to public, max-age=7200.

4. Build the project, and do the same as Step 3, but you'll see Cache-Control set to no-cache, no-store, must-revalidate

Expected behavior

I expect that Cache-Control header to be same as set in getServerSideProps either in dev or production build.

System information

• OS: macOS
• Browser: Chrome
• Version of Next.js: 9.3.0

Additional context

I was able to reproduce the issue in a new next.js project.

[dulmandakh]

Thanks 🙏

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.