On 25/11/18 5:24 am, Heiler Bemerguy wrote: > No doubt, the connections were really being closed by the proxy itself, > LIKE it was finished sending the request. It was like a loop, so it was > infinite connections one right after another, but not in parallel.. the > fin-packets and everything else were "in order" judgjing by their SEQ > values too. > > There were other refresh_patterns but none matching it. I didn't enable > debug options but I can try to reproduce it.. anyway the .conf was like > that for years and this was the first time a "loop" like this occurred. > I upgraded from 3.5.27 to 3.5.28 but I think nothing about this was > modified recently, right..? > 3.5.28 is now treating the Content-Range header better - ignoring it in server responses where it is not valid. Older versions were truncating responses. Wild guess but I suspect the object stored in cache previously may have been one of those incorrectly truncated ones or something like that. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
