title: Google Chrome Developer Toolbar says an image doesn't have a cache expiration, but it seems like it does
body: <p>An example, <a href="https://www.google.com/intl/en_com/images/srpr/logo3w.png" rel="nofollow">Google's own logo</a>  If you go to either <a href="http://www.google.com" rel="nofollow">www.google.com</a> or the [URL of the image</p>
  
  <p>and run a page audit using the Developer Toolbar, you'll get a message to take advantage of browser caching, viz. <code>The following resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers: logo3w.png</code>.</p>
  
  <p>Then, if you look at the actual headers, e.g. <a href="http://web.forret.com/tools/analyze.aspx?url=https%3A%2F%2Fwww.google.com%2Fintl%2Fen_com%2Fimages%2Fsrpr%2Flogo3w.png" rel="nofollow">via</a>, they read:</p>
  
  <pre><code>* Content-Type = image/png
  * Last-Modified = Fri, 05 Aug 2011 02:40:26 GMT
  * Date = Fri, 30 Dec 2011 20:53:48 GMT
  * Expires = Fri, 30 Dec 2011 20:53:48 GMT
  * Cache-Control = private, max-age=31536000
  * X-Content-Type-Options = nosniff
  * Server = sffe
  * Content-Length = 7007
  * X-XSS-Protection = 1; mode=block
  </code></pre>
  
  <p>What's the deal?</p>
  
  <p><strong>UPDATE</strong> :: MattH points out that the <code>Expires</code> time is the same as the request.  True!  I think there's still a problem; check out <a href="http://s3.amazonaws.com/thesprouts-org/public/images/linen.jpg" rel="nofollow">this image</a>.</p>