title: Would browsers set If-Modified-Since or If-None-Match header in the new request after being redirected?
body: <p>So I'm testing with this setup. <code>https://example.com/original</code> always responds with a 308 status code, redirecting the browser to <code>https://example.com/new</code>.
  <code>https://example.com/new</code> checks if <code>If-Modified-Since</code> and <code>If-None-Match</code> to see if cache is still valid, and returns 304 if so. Otherwise it should return 200 with the full content and ETag, Last-Modified in response header.</p>
  <p>What I'm seeing is that after being redirected, however many times I try, in the new request to <code>https://example.com/new</code> the browser does not have <code>If-Modified-Since</code> or <code>If-None-Match</code> set. Thus the server always return 200 with the full content. It feels like browser just does not try to remember ETag or <code>Last-Modified</code> returned by <code>https://example.com/new</code>.</p>
  <p>Is it possible for the redirect response (<code>https://example.com/original</code> which returns 308) to tell the browser to remember ETag or Last-Modified so it can include If-Modified-Since or If-None-Match in the request to <code>https://example.com/new</code>?</p>