> Some clients are now starting to support the Expires header, but I know of
> none that will automatically refresh without user intervention. If they
> do then there is a need for a second header: one that tells the client
> that the document will expire at some given time - but don't bother
> getting it again.
Isn't it fun, trying to introduce advanced concepts of state to a
stateless protocol.
Is http going to keep mutating to provide the things people need, or is
state going to be obtained some other way?
-- Paul Phillips EMAIL: psp@ucsd.edu PHONE: (619) 220-0850 WWW: http://www.primus.com/staff/paulp/ FAX: (619) 220-0873