W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2003

Re: Problems with caching header values

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 23 Aug 2003 13:00:44 -0700
Cc: <ietf-http-wg@w3.org>
To: "Wilfred Nilsen" <wilfred.nilsen@cox.net>
Message-Id: <7B255971-D5A4-11D7-8D55-00039396E15A@mnot.net>

Keep in mind that caches aren't obliged to cache when headers allow it; 
they may have strategies that they believe work better.

In my experience, browser caches are pretty simplistic, and very 
conservative. They may have the images inheriting freshness information 
from the page they're referenced from, or they may interpret the 
refresh tag as a forced refresh for everything on the page.

Cheers,


On Thursday, August 21, 2003, at 02:30  PM, Wilfred Nilsen wrote:

>
> I have a page that is generated dynamically and I therefore set the
> "Cache-Control: No-Cache" header. The page contains a meta refresh tag
> and is automatically polled every so often.
>
> The page contains links to images that never change so in order to
> prevent the browser from attempting to fetch new versions of the
> images, I set the header value "Cache-Control: max-age=86400". The
> problem is that the browsers I have tested this with, IE 6.0 and
> Mozilla 1.13, seems to ignore the max-age header value and are always
> checking for newer versions. The browsers are set to get a new page
> when the current page is out of date.
>
> I also tried to set the "Expires" header but that did not help either.
>
> Thanks,
> Wilfred
>
Received on Saturday, 23 August 2003 16:00:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:23 GMT