Hi,
I have just update to the latest version, and the results are clear:
cat /var/log/squid/access.log | awk '{print $4}' | sort | uniq -c | sort -rn
486561 TCP_MISS/200
89612 TCP_MISS/304
52123 TCP_MEM_HIT/200
40408 TCP_MISS/206
36267 TCP_MISS/302
20904 TCP_MISS/204
12246 TCP_IMS_HIT/304
12171 TCP_MISS/404
10533 TCP_MISS/301
9145 TCP_MISS/000
6004 TCP_OFFLINE_HIT/200
......
It's said that MISS/301, MISS/303 are not cacheable without special
instructions.
What are those SPECIAL instructions?
On 21 August 2014 00:46, Amos Jeffries <squ...@treenet.co.nz> wrote:
> On 21/08/2014 6:05 a.m., Délsio Cabá wrote:
>> Hi,
>> Using version: Squid Cache: Version 3.1.10 (Centos RPM)
>>
>
> Ah. The version itself is probably most of the prooblem.
>
> 3.1 does not cache traffic with Cache-Control:no-cache, which these days
> consists of a large percentage (30-40) of all traffic. That is resolved
> in 3.2 and later, along with better caching of private and authenticated
> traffic.
>
> You can find details of newer CentOS RPM packages from Eliezer at
> http://wiki.squid-cache.org/KnowledgeBase/CentOS
>
> Amos
>
