Tilman Mueller-Gerbes wrote:
> It seems as if Netscape's home site does respond with a META
> Refresh tag and a Refresh interval of 0 seconds.
META Refresh is only for telling the client that it should refresh it's
view of the page. It says nothing about cachability or when a cache
should refresh it's cached copy as it is a pure client-side tag.
Using "Refresh 0" is wierd, as it forces the browser to constantly
refresh the page.
> This confuses Netscape 4.06 in a weird way: it always refetches
> the page and gets a TCP_MEM_HIT and requests the page and gets a
> TCP_MEM_HIT and ... Going directly there works, though.
It shouldn't work going directly either. Maybe they return a different
response on the second refresh?
> Is this a known problem? Maybe Squid does not handle the
> refresh 0 secs
If they want caches to refresh the page then they need to use Expires:
as well (or perhaps a Cache-Control: max-age directive is more
appropriate here).
--- Henrik Nordstrom Spare time Squid hackerReceived on Thu Oct 22 1998 - 15:05:05 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:45 MST