hey guys, forgot-me? :(
2015-09-17 8:08 GMT-03:00 Jorgeley Junior <jorge...@gmail.com>:
> thank you all for the reply, here is the result of the command:
> 1 TAG_NONE/500
> 290 TAG_NONE/503
> 10 TAG_NONE_ABORTED/000
> 4 TCP_CLIENT_REFRESH_MISS/200
> 368 TCP_DENIED/403
> 1421 TCP_DENIED/407
> 5 TCP_HIT/200
> 7 TCP_HIT_ABORTED/000
> 7 TCP_IMS_HIT/200
> 39 TCP_IMS_HIT/304
> 1 TCP_MEM_HIT/200
> 680 TCP_MISS/200
> 39 TCP_MISS/204
> 1 TCP_MISS/206
> 9 TCP_MISS/301
> 30 TCP_MISS/302
> 70 TCP_MISS/304
> 8 TCP_MISS/404
> 29 TCP_MISS/416
> 1 TCP_MISS/500
> 3 TCP_MISS/503
> 16 TCP_MISS_ABORTED/000
> 4 TCP_MISS_ABORTED/200
> 1 TCP_MISS_ABORTED/206
> 56 TCP_REFRESH_MODIFIED/200
> 1 TCP_REFRESH_MODIFIED/416
> 38 TCP_REFRESH_UNMODIFIED/200
> 192 TCP_REFRESH_UNMODIFIED/304
> 3 TCP_SWAPFAIL_MISS/200
> 10 TCP_SWAPFAIL_MISS/304
> 1896 TCP_TUNNEL/200
>
>
> 2015-09-17 2:12 GMT-03:00 Amos Jeffries <squ...@treenet.co.nz>:
>
>> On 17/09/2015 8:55 a.m., Eliezer Croitoru wrote:
>> > Try to run this on you access.log:
>> > cat /var/log/squid/access.log|gawk '{print $4}'|sort|uniq -c
>> >
>> > This should show a list of all the cases which includes 304 status code.
>> > If you can post the results there will might be another side to the
>> > whole story in the output.
>> >
>> > Eliezer
>>
>> Yes that should clarify the story a bit. As would the Squid version
>> details.
>>
>> What is clear is that over 60% of the traffic by both count and volume
>> is neither HIT nor MISS. The graphing / analysis tool does not account
>> for TUNNEL or REFRESH transactions which can happen in HTTP/1.1.
>>
>> Amos
>>
>>
>> _______________________________________________
>> squid-users mailing list
>> squid-users@lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
>>
>
>
>
> --
>
>
>
--
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
