title: Is Chrome ignoring Cache-Control: max-age?
body: <p>Background:</p>
  
  <ul>
  <li>IIS 7 </li>
  <li>AspNet 3.5 web app</li>
  </ul>
  
  <p>Chrome dev tools lists 98 requests for the home page of the web app (aspx + js + css + images). In following requests, status code is <code>200</code> for css/images files. No cache info, browser asks server each time if file has to be updated. OK.</p>
  
  <p>In IIS 7 I set HTTP header for cache control, set to 6 hours for the "ressources" folder. In Chrome, using dev tools, I can see that header is well set in response:</p>
  
  <pre><code>Cache-Control: max-age=21600
  </code></pre>
  
  <p>But I still get 98 requests... I thought that browser should not request one ressource if its expiration date is not reached, and I was expecting the number of requests to drop...</p>