re: Cache-Control header cannot be set properly in ASP.NET 2.0 - A solution

David Stevenson — Tue, 08 Jan 2008 19:58:37 GMT

I am getting a max-age of 9999999 and TWO Cache-Control headers. the max-age of 9,999,999 seconds, or about 115 days, which conflicts with my setting of 365 days in the Expires HTTP header. I am wondering why I am getting TWO Cache-Control headers, and a max-age I didn't specify.

HTTP/1.1 200 OK

Server: Microsoft-IIS/5.0

Date: Tue, 08 Jan 2008 19:49:41 GMT

X-Powered-By: ASP.NET

Cache-Control: public, max-age=9999999

X-AspNet-Version: 2.0.50727

Cache-Control: public

Expires: Wed, 07 Jan 2009 19:49:41 GMT

Last-Modified: Thu, 28 Jul 2005 22:08:28 GMT

Content-Type: image/gif

Content-Length: 2306

resp.Cache.SetExpires(DateTime.Now.AddSeconds(365 * 24 * 60 * 60)); // Expires in one year.

// Public - Allows the response to be cached by clients and shared (proxy) caches.

resp.Cache.SetCacheability(HttpCacheability.Public);

resp.Cache.SetValidUntilExpires(true);

FileInfo file = new FileInfo(path);

resp.Cache.SetLastModified(file.LastWriteTimeUtc);

David Stevenson

re: Cache-Control header cannot be set properly in ASP.NET 2.0 - A solution

Milan — Wed, 19 Sep 2007 06:25:09 GMT

Hi,

What abount 3.x version of frameworks? Do they have the same issue?