As all the objects seem to expire NEVER that means that whatever I specify
in the refresh rules has no effect. So the pages which ?I want to expire in
24 hours would not expire, then the question is what is the point of
specifying the refresh rules. e.g I want www.cnn.com to expire in 12 hours
but it is showing NEVER. Will cnn.com be refreshed after 12 hours or will
the users get stale page. So do I make it expire in 12 hours.
Thanks,
Irfan Akber
----------
From: John Dilley <jad@porter.hpl.hp.com>
To: Irfan Akber <irfan@inet.com.pk>
Cc: squid-users <squid-users@ircache.net>
Subject: Re: Cache size confusion
Date: Wednesday, October 28, 1998 2:47 PM
> > > Upon looking at cachemgr result I get
> > >
> > > 5.http://www.infoseek.com/
> > > Verified 1m ago, Used 1m ago, Modified 1m ago, Expires in 13h,
> > > 24955 bytes, 1 accesses, 0 active clients,
> > > STORE_OK, IN_MEMORY, SWAP_OK, PING_NONE,
> > > 0 Locks, Flags: EC,KU,HT,ED,HI
> > > 6.http://www.infoseek.com/images/tmpl/swoop.gif
> > > Verified 1m ago, Used 1m ago, Modified 1M ago, Expires NEVER,
> > > 196 bytes, 1 accesses, 0 active clients,
> > > STORE_OK, IN_MEMORY, SWAP_OK, PING_NONE,
> > > 0 Locks, Flags: EC,KU,HT,ED,HI
> > >
> > > Why the expiry is NEVER when I have min time 4 days and max 1 month
in
> > > refresh pattern.
> > >
> >
> > Irfan,
> > The Expires field is from the content HTTP headers, not from
> > your cache settings. Same with Modified. Regards,
>
> But how is it possible that all the objects have expiry as NEVER when
> looking at the Objects in cache.
Irfan,
In the example above one of your objects never expires, the
other in 13 hours. It would be possible for all of your objects to
expire NEVER, however, if all depends upon the content your users
accessed and their Expires headers. Expires of never is used whenever
the expires time (in the source) is negative. Regards,
-- jad --
John Dilley <jad@hpl.hp.com>
Received on Wed Oct 28 1998 - 08:31:32 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:50 MST