Re: [squid-users] TCP_IMS_HIT/304 or TCP_REFRESH_HIT/304

Hi ,

a) We can ensure by setting the Object expire value for a time of longer
duration .

b) TCP_HIT will come into picture if every check is OK! (ie :- Object is
Fresh).

c) If you want to have the TCP_HIT for the the same Object.

Modify the Last-Modified header to current date of requested Object in the
Apache Server, Fresh copy will be cached in the squid.

As long as the Object is valid it may give TCP_HIT or TCP_MEM_HIT.

I would be thankful ,if anybody can provide me information about the
calculation of AGE and refresh check in squid caching mechanism

thanks
senthil

Simon Meddings wrote:

> Is there ways to ensure these objects are not expired and actually serve
> them from squid rather than contacting the original server again?
>
> >The Orgin Server replies with 304 Not Modified, (content not
> >modified).
> >So squid logs TCP_REFRESH_HIT or TCP_IMS_HIT.
> if the page is requested again normally then I still get the TCP_IMS_HIT!
> surly this should read TCP_HIT/200?!?!
>
> it's kind of defeating the purpose of have a caching server at the moment!!
>
> any ideas?
>
> Cheers
> Simon.
>
> At 11:24 22/05/2002, you wrote:
> >Hi ,
> >
> > The logs informs that cached object in the Squid got expired. So
> >request will be
> >sent to Orgin server.
> > The Orgin Server replies with 304 Not Modified, (content not
> >modified).
> >So squid logs TCP_REFRESH_HIT or TCP_IMS_HIT.
> >
> >thanks
> >senthil
> >
> >
> >
> >Simon Meddings wrote:
> >
> > > Hi,
> > >
> > > looking at the squid access logs I dont seem to get any TCP_HIT/200,
> > > instead I either get
> > > TCP_IMS_HIT/304 or TCP_REFRESH_HIT/304 or TCP_MISS/[200|301]
> > >
> > > any idea's??
> > >
> > > Thanks in advance
> > >
> > > Simon.
Received on Wed May 22 2002 - 05:07:07 MDT