Geeks With Blogs
urig Tidbits from a .net life

I usually post about problems that I've solved. But every once in a while, for all my digging around and googling, I come up on something that I can't solve quickly and thuroughly enough - so I post about it here in the hope someone can help.

To make a long story short - I've found out that FireFox 1.5 appends a "Cache-Control: max-age=0" HTTP header to requests for ASPX files. This header tells the web server and any proxy servers on the way not to respond with cached version of the requested page and to go and run the actual ASPX instead.

For me, this is a big problem. It renders the NetApp NetCache reverse proxy that I'm using quite useless and impacts badly on response times for that particular page.

Does anybody know why FireFox adds this header to the request? How can this be circumvented either on the browser's side or on the proxy server's side?

Thanks!
urig

Posted on Thursday, November 2, 2006 10:29 AM | Back to top



Comments on this post: FireFox and Cache-Control: max-age=0

# re: FireFox and Cache-Control: max-age=0
Requesting Gravatar...
Hello, I've run into the same "problem", however I dont know if the problem lies on Firefox or on OutputCacheModule which does a calculation to check if the content actually changed.

Left by hammett on Nov 11, 2006 10:05 PM

# re: FireFox and Cache-Control: max-age=0
Requesting Gravatar...
I'm not sure how OutputCacheModule on the ASP.Net side can be blamed for this, as the header seems to originate from the FireFox browser itself.

Can you elaborate on that you've written above?
Left by urig on Nov 12, 2006 3:01 PM

# re: FireFox and Cache-Control: max-age=0
Requesting Gravatar...
I've explained what I've found yesterday, but then geekswithblogs fell with a OutOfMemory exception. Strange...

My find is that the maxage=0 is only sent if you hit F5 (refresh) which Firefox understand as a request to really get the latest content, thus bypassing any cache. It's different from IE, but nevertheless it's a quite right behavior. If you access page1.ext (cached) then access page2.ext (cached) and back page1, you'll notice that the max age will not be sent.
Left by hammett on Nov 12, 2006 5:14 PM

# re: FireFox and Cache-Control: max-age=0
Requesting Gravatar...
@hammett thanks for the f5 tip!
Left by paul on May 06, 2009 9:34 AM

Your comment:
 (will show your gravatar)


Copyright © urig | Powered by: GeeksWithBlogs.net