Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Eliezer Croitoru
-cache.org Subject: Re: [squid-users] time based range_offset_limit 1468423415.143 160645 10.1.4.7 TCP_MISS_ABORTED/206 510 GET http://au.v4.download.windowsupdate.com/d/msdownload/update/software/secu/2016/06/word-x-none_48e3c2f2bb14dd57321ae5a53cf8de2ca0fe6114.cab - HIER_DIRECT/201.48.38.146

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Heiler Bemerguy
1468423415.143 160645 10.1.4.7 TCP_MISS_ABORTED/206 510 GET http://au.v4.download.windowsupdate.com/d/msdownload/update/software/secu/2016/06/word-x-none_48e3c2f2bb14dd57321ae5a53cf8de2ca0fe6114.cab - HIER_DIRECT/201.48.38.146 application/octet-stream 1468423415.146 160651 10.1.4.7 TCP_MISS_ABO

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Omid Kosari
Amos Jeffries wrote > Though be aware that Squid being Internet software operates using UTC > timezone. Not local wall-time. After many try and false i can confirm that the time is NOT UTC and it is local time !! Recheck plz -- View this message in context: http://squid-web-proxy-cache.101909

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Amos Jeffries
On 14/07/2016 12:43 a.m., Heiler Bemerguy wrote: > > Em 12/07/2016 23:43, Alex Rousskov escreveu: >> >>> (without using Range: header). >> That's your squid.conf customization, I presume. >> > > The squid won't send a Range: header to the server because the request > is matching the range_offset_

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Heiler Bemerguy
Em 12/07/2016 23:43, Alex Rousskov escreveu: (without using Range: header). That's your squid.conf customization, I presume. The squid won't send a Range: header to the server because the request is matching the range_offset_limit -1 ACL. I presume. So squid will try to fetch the file fr

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Omid Kosari
Amos Jeffries wrote > Though be aware that Squid being Internet software operates using UTC > timezone. Not local wall-time. Good point , Thanks Amos Jeffries wrote > Whether that behaviour will "work" for whatever your problem actually is > nobody knows, because you did not state what the probl

Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Amos Jeffries
On 12/07/2016 11:14 p.m., Omid Kosari wrote: > Hello, > > I want to have "range_offset_limit none" for specific acl in specific time . > The config is and squid -k parse/check does not show any error . > > acl download_until_end_by_ip dst 13.107.4.50 > acl freetimes time 03:00-08:00 > range_offs

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Alex Rousskov
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

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Heiler Bemerguy
Em 12/07/2016 18:30, Alex Rousskov escreveu: Said that, some special clients do send concurrent *Range* requests for the same URL! If Squid receives N concurrent Range requests for the same URL, I believe Squid will try to collapse them, possibly with disastrous results, especially if Squid doe

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Heiler Bemerguy
10.1.10.9 is the proxy's IP, dude And it is connecting to the same server multiple times because a client is doing a RANGE download.. (windows update to be exact) All GETS are like these: GET http://au.v4.download.windowsupdate.com/d/msdownload/update/software/defu/2016/06/am_base_7684a3445

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Alex Rousskov
On 07/12/2016 02:08 PM, joe wrote: >>> collapsed_forwarding on > this is good if you have other client downloading on same time same file it > has nothing to do with multi connection to the same ip only it will help > saving you example if you have 10 client downloading at the same time same > f

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread joe
>>root@proxy:~# netstat -n |grep 201.30.251.27 |grep ESTAB >>tcp 243802 0 10.1.10.9:27788 201.30.251.27:80ESTABELECIDA >>tcp0 0 10.1.10.9:15343 201.30.251.27:80ESTABELECIDA >>tcp14480 0 10.1.10.9:32548 201.30.251.27:80ESTABELECIDA >>tcp0

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Heiler Bemerguy
Hello Joe, I've tried doing that but it seems collapsed_forwarding won't work for windows updates for some reason.. it's really annoying. Look the number of simultaneos connections to the SAME ip... this shouldn't happen, right? root@proxy:~# netstat -n |grep 201.30.251.27 |grep ESTAB tcp

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread joe
>acl download_until_end_by_ip dst 13.107.4.50 >acl freetimes time 03:00-08:00 >range_offset_limit none download_until_end_by_ip freetimes wen you have simultaneous connections on one large file update try that collapsed_forwarding on <- enable that will help if there is lots a connecti

Re: [squid-users] time based range_offset_limit

2016-07-12 Thread Heiler Bemerguy
You're having problems with huge bandwidth being used by simultaneous connections from the proxy? All of them to the same IP, getting the same file in paralell ?? -- Best Regards, Heiler Bemerguy Network Manager - CINBESA 55 91 98151-4894/3184-1751 Em 12/07/2016 08:14, Omid Kosari escreve

[squid-users] time based range_offset_limit

2016-07-12 Thread Omid Kosari
Hello, I want to have "range_offset_limit none" for specific acl in specific time . The config is and squid -k parse/check does not show any error . acl download_until_end_by_ip dst 13.107.4.50 acl freetimes time 03:00-08:00 range_offset_limit none download_until_end_by_ip freetimes But please