On 07/12/2016 03:56 PM, Heiler Bemerguy wrote: > (if the first one had already received at > least the replying HEADER of the server) That is not collapsed forwarding. That is regular caching. Collapsed forwarding covers the time range from the first parsed request header until the corresponding response header is parsed. > (without using Range: header). That's your squid.conf customization, I presume. > After the server starts sending the data, squid will correctly forward > the traffic to the clients. Each one will get the range it asked for.... That's expected. > That's why I don't understand why it does not work on a REAL > enviroment. Many things can go wrong -- the real requests may require collapsed forwarding that you do not test, the real requests may have no-cache, the real response may not be cachable, or there is some Range handling bug that your test scripts do not tickle (e.g., they request ranges that are always close to each other and are always available at the same time). You need to figure out the difference between your test and the real world. Comparing test and real access.log might help. If that does not help, you can try capturing incoming/outgoing traffic. You can also try your test script against the real Squid. Does it still work? Beyond that, you would have to do detailed traffic analysis (packet captures; ALL,2; ALL,9). Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
