Question

I have just started using OutputCache on some of my controller actions and I am not quite getting the response I would expect.

I have set the cache time to 5 minutes and the Expires header is coming up the same as the Last-Modified header which is the time that the request was made.

This is the header I am currently getting:

Date                    Thu, 16 Jul 2009 06:35:07 GMT
Server                  Microsoft-IIS/6.0
X-Powered-By            ASP.NET
X-AspNet-Version        2.0.50727
X-AspNetMvc-Version     1.0
Content-Encoding        gzip
Cache-Control           public, max-age=300
Expires                 Thu, 16 Jul 2009 06:35:06 GMT
Last-Modified           Thu, 16 Jul 2009 06:35:03 GMT
Vary                    *
Content-Type            text/html; charset=utf-8
Content-Length          575

This is the header I would expect:

Date                    Thu, 16 Jul 2009 06:35:07 GMT
Server                  Microsoft-IIS/6.0
X-Powered-By            ASP.NET
X-AspNet-Version        2.0.50727
X-AspNetMvc-Version     1.0
Content-Encoding        gzip
Cache-Control           public, max-age=300
Expires                 Thu, 16 Jul 2009 06:40:06 GMT
Last-Modified           Thu, 16 Jul 2009 06:35:03 GMT
Vary                    *
Content-Type            text/html; charset=utf-8
Content-Length          575

Any ideas on why it would be doing this?

Cheers
Anthony

Answer 1

max-age takes precedence (from RFC 2616):

We use the term expires_value to
denote the value of the Expires
header. We use the term
max_age_value to denote an
appropriate value of the number of
seconds carried by the “max-age”
directive of the Cache-Control header
in a response (see section 14.9.3).

The max-age directive takes priority
over Expires, so if max-age is present
in a response, the calculation is
simply:

  freshness_lifetime = max_age_value 

Otherwise, if Expires is
present in the response, the
calculation is:

  freshness_lifetime = expires_value - date_value

So the client should use the cached version as you expect.