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

From: Simon Meddings <simon.meddings@dont-contact.us>
Date: Wed, 22 May 2002 11:38:06 +0100

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 - 04:37:48 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:11 MST