FireFox and Cache-Control: max-age=0

November 1, 2006

one comment

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?


Add comment
facebook linkedin twitter email

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


one comment

  1. Daniel O'ConnorDecember 7, 2006 ב 6:43 am

    It took us a bit to work it out.

    If you hit refresh, firefox will ask for the latest copy (max-age=0).

    If you type the url into the address bar and hit enter, then type it in again, it’ll cache.

    Check it works in about:cache.

    See also: