On 4/11/2015 11:53 a.m., HackXBack wrote: > what joe is going to tell us is that his HIT ratio decrease and he is seeing > TCP_REFRESH_MODIFIED instead of tcp_hit when he used V4 > this problem is right also with tcp swalfail miss I don't think the two are the same at all. REFRESH is (in jo's case) an indicator that the private content is being checked before use. If the server behaves itself the answer would be UNMODIFIED/304 not MODIFIED/200 status, and the transfer size under 1KB. SWAPFAIL is errors loading the on-disk file where the object ws stored in the cache. Unless you want to serve random bytes out to the client that failure will always have a MISS/200 or DENIED/500 result. In your case the bug is that you are having the disk I/O failure at all. jo is not. > with V3.4 these strange problems is not exists .. > 3.4 does not cache several of the types of objects that 3.5+ do. We are still in the process of converting Squid from HTTP/1.0 behaviour to HTTP/1.1 behaviour. It is going slowly, one step at a time. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
