title: default cache-control headers in nextjs SSR
body: <p>I have <code>nextjs</code> app. If I add <code>getServerSideProps</code> export to the page (this means that page will be server side rendered, <a href="https://nextjs.org/docs/basic-features/data-fetching/get-server-side-props" rel="nofollow noreferrer">read more</a>) <code>nextjs</code> adds <code>cache-control</code> header:</p>
  <pre><code>cache-control: private, no-cache, no-store, max-age=0, must-revalidate 
  </code></pre>
  <p>But according to this <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#preventing_storing" rel="nofollow noreferrer">documentation</a> these are conflicting headers and in theory it should be the same as <code>no-store</code> header. Citing the acticle:</p>
  <pre><code># conflicted
  Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
  
  # equivalent to
  Cache-Control: no-store
  </code></pre>
  <p>Is there any reason these multiple headers are used instead of simply using <code>no-store</code>?</p>