> Can someone be so kind to explain me if the default values for the
> refresh_patern (0 20 4320) violates any HTTP specifications?
One thing to bear in mind when trying to cache very aggressively is
that at some point your users will simply do shift reload in
Netscape, which will increase your traffic. Once that happens you
will be forced to treat this as a revalidate request (violating the
protocol) and will start losing customers. (In particular, they are
likely to do shift reload for everything once they suspect you are
serving very stale data.)
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.
(An other point is that many sites don't want you to cache.)
-- David Woolley - Office: David Woolley <djw@bts.co.uk> BTS Home: <david@djwhome.demon.co.uk> Wallington TQ 2887 6421 England 51 21' 44" N, 00 09' 01" W (WGS 84)Received on Fri Mar 19 1999 - 09:56:51 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:45:21 MST