David J Woolley wrote:
>
> A better approach would be for them to use max-age, to simply defeat
> your refresh pattern put allow conditional GETs, but that is not
> normally available in browsers and shift reload is easier anyway.
I wouldn't be so sure about this. Netscape 4.5.x _does_ appear to send a
MaxAge periodically, although I've not been able to pin down the
circumstances, exactly. I think it's when a copy of an object already
exists in it's browser cache and it's revalidating it. Maybe.
D
