RE: [squid-users] http request not caching Please Help..!!!

Hi Colin,

Thanks for your reply but every subsequent
retrieval has exactly the same lines in the access.log file.

Thanks

Lakshman
-----Original Message-----
From: Colin Campbell [mailto:sgcccdc@citec.qld.gov.au]
Sent: Tuesday, 5 March 2002 12:22 PM
To: SRILAKSHMANAN,LAKSHMAN (HP-Australia,ex3)
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] http request not caching Please Help..!!!

Hi,

On Tue, 5 Mar 2002, SRILAKSHMANAN,LAKSHMAN (HP-Australia,ex3) wrote:

> Hi all,
>
> Why is squid not caching http request? I always get TCP_MISS..!!!

You only showed two log entries.

> My URL http://panther.aus.hp.com/soar.tar generates the following in the
> squid access.log
>
> 1015286365.529 1 15.73.168.201 TCP_MISS/401 743 GET
> http://panther.aus.hp.com/soar.tar - DIRECT/panther.aus.hp.com text/html
> 1015286377.137 5672 15.73.168.201 TCP_MISS/200 2171213 GET
> http://panther.aus.hp.com/soar.tar - DIRECT/panther.aus.hp.com
> application/x-tar

I suspect the first GET was not cached because it was denied by the web
server returning a "401". You can see the content length returned was 743
bytes - probably the authorization request. After that was the successful
GET which returned 2171213 bytes. Whether it was cached or not is not
vissible in this log. Look at store.log to see what happened with this
successful retrieval. What does the access log show on subsequent
retrievals?

Colin
Received on Mon Mar 04 2002 - 18:31:31 MST