On 16/04/2015 9:09 a.m., HackXBack wrote: > hello minds, > it seems many files appear in access.log as 206 and not 200, > to make this file hit is by using range_offsit_limit none > but this option cause squid to consume more bandwidth from real internet, > so what is the solution to make 206 cached and hit again without make it > consume this huge bandwidth ? Is that MISS/20 or HIT/206. Big difference. Also whether the object(s) are cacheable at all also makes a big difference. No use fetching all that unwanted bytes if the object is just going to be thrown away. range_offset_limit none with quick_abort* settings to allow the objects to finish downloading after the clients are done is how you get the object to be 200 from the server, and fully available for storage - assumign it can be cached. That only works if the 206 are for the same objects repeatedly. If they are for parts of different objects all the time or the objects are not cacheable, then dont worry. 206 is the most efficient form of transfer for that type of traffic. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
