authenticated requests are not cache-able unless over write by
Cache-control: public in server respond.
Ming
On 01/04/2010 11:12 PM, Mike Makowski wrote:
I have attached is a screenshot of WGET header output with the "-S" option.
I see nothing about "private" in the headers so I'm assuming this content
should be getting cached. Yet, each time I run wget and then view the Squid
access log it shows TCP_MISS on every attempt. I'll try the Ignore Private
parameter in squid just to make sure that isn't the cause.
Very puzzling.
Mike
-----Original Message-----
From: Chris Robertson [mailto:crobert...@gci.net]
Sent: Monday, January 04, 2010 6:48 PM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Forward Cache not working
Mike Makowski wrote:
Here is my basic config. Using defaults for everything else.
acl localnet src 172.16.0.0/12
http_access allow local_net
maximum_object_size 25 MB
Here is a log entry showing one connection from a LAN user through the
proxy. I am guessing that the TCP_MISS is significant. Perhaps the
original source is marked as Private as Chris suggested. Don't really know
how to even tell that though.
Add a "-S" to wget to output the server headers.
wget -S http://www.sortmonster.net/master/Updates/test.xyz -O test.new.gz
--header=Accept-Encoding:gzip --http-user=myuserid --http-passwd=mypassword
Can squid be forced to cache regardless of
source settings?
Yes. http://www.squid-cache.org/Versions/v3/3.0/cfgman/refresh_pattern.html
Keyword "ignore-private".
1262645523.217 305633 172.17.0.152 TCP_MISS/200 11674081 GET
http://www.sortmonster.net/master/Updates/test.xyz - DIRECT/74.205.4.93
application/x-sortmonster 1262645523.464 122
Mike
Chris
