Hey, Your words describe the BUG in his wildest and simplest form. Please file a bug report to follow the progress. Writing here more and more will not be really a good help as it is. Eliezer On 15/03/2016 19:51, Heiler Bemerguy wrote:
Hi joe, Eliezer, Amos.. today I saw something different regarding high bandwidth and caching of windows updates ranged requests.. A client begins a windows update, it does a: HEAD to check size or something, which is ok.. then a ranged GET, which outputs a TCP_MISS/206, then the next GET gives a TCP_SWAPFAIL_MISS/206. Lots of other TCP_MISS/206, then in the end, TCP_MISS_ABORTED/000 A big amount of parallel connections are being made because of each GET.. ok, I know squid can't do much about it.. but then, why the content does not get cached in the end? I mean, the way it is, it will happen every day.. are these "TCP_MISS_ABORTED" really the client aborting the download? I doubt it... Take a look and see if you can understand:
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
