I implemented squid 3.0 on a home system largely to help reduce Internet
traffic (I am forced to use a 3G/cell-based connection that has high excess
bandwidth charges). I used the default configuration - the only major changes
were defining a 4GB cache and adding ACLs to block ad sites.
Squi
In digging through my squid 3.0 access.log, I noticed a TCP_MISS for the same
file fetched twice in a relatively short period of time. The store.log shows
that the file was RELEASEd.
1259160356.949 RELEASE -1 176C2C1221D157A9EC778A2D08E70AFF 200
1259160364-1-1 text/
> Your squid.conf default settings might have "acl QUERY url_regex cgi-bin
> \?", "cache deny QUERY", or the nicer "refresh_pattern -i (/cgi-bin/|\?)
> 0 0% 0" to tell squid explicitly what requests to consider dynamic. But
> the defaults are not involving .shtml
I did not find any "cache deny
Amos, thanks for the fast response!
> Not certain. But I suspect it has something to do with small browser
> caches. The defaults I've seen on client boxes are usually in the MB
> ranges. Large enough for a few dozen flash media videos and little else.
> Your 4GB in Squid could be making up the
Although my squid server is only supporting three users, I am pleasantly
surprised at the percentage of traffic handled by the cache. However, I think
I can do better. Scanning the logs, I noticed a number of cases where the same
files were resulting in a TCP_MISS/200 condition. A lot are due
Chris, nothing like those statements in my squid.conf.
Thanks, Norbert
> Chris Robertson wrote:
> Making sure you don't have...
>
> acl QUERY urlpath_regex cgi-bin \?
> cache deny QUERY
>
> ...in your squid.conf, in conjunction with the refresh_patterns you DO
> have are about as far as yo
Amos, assuming Facebook does not listen, is there a way around invalid dates?
I have added the '-i' option to the refresh_pattern. I do not have any other
refresh_patterns defined. I like to keep things simple if I can.
Thanks, Norbert
>Amos wrote:
>> General: The Expires header's valu
I enabled level 6 logging for section 22 and 65. I then explicitly retrieved
'http://www.facebook.com/images/loaders/indicator_blue_small.gif' and found the
following entries in cache.log. Does this confirm that the problem is the
invalid 'Expires' header value? If so, is there a way around t
