title: Google Chrome does not revalidate etag on back/forth
body: <p>Even though I send "cache-control: must-revalidate" Google Chrome uses a locally cached page when using the back and forth button in the browser.</p>
  
  <p>This is part of the original response:</p>
  
  <pre><code>HTTP/1.1 200 OK
  cache-control: private, must-revalidate
  etag: "c9239b5d4b98949f8469a05062e05bb999d7512e"
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html; charset=utf-8
  </code></pre>
  
  <p>If I refresh the page I get a "HTTP/1.1 304 Not Modified" response but when I use the back button I get the following response:</p>
  
  <pre><code>Request URL:example.com
  Request Method:GET
  Status Code:200 OK (from cache)
  </code></pre>
  
  <p>The response I'm looking for is 304 or 200 OK, is it possible to achieve this?</p>