Re: [squid-users] time based range_offset_limit

2016-07-13 Thread Eliezer Croitoru
Just to add the Microsoft BITS client uses a If-Unmodified-Since header and not a no-cache. The above is as far as I can tell from dumps I have for windows 7 and up. There are cases which a client would want to abort the connection but I have not seen these from windows for a long time. Eliezer

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] assertion failed: DestinationIp.cc:41: "checklist->conn() && checklist->conn()->clientConnection != NULL"

2016-07-13 Thread Amos Jeffries
On 13/07/2016 1:33 a.m., Omid Kosari wrote: > Hello, > > squid crashes after following error > assertion failed: DestinationIp.cc:41: "checklist->conn() && > checklist->conn()->clientConnection != NULL" > > > From the error massage i guess that following config may cause the problem > > #acl do

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] url_rewrite_program shows IP addresses instead of domain name when rewriting SSL/HTTPS

2016-07-13 Thread Amos Jeffries
On 13/07/2016 5:46 a.m., Moataz Elmasry wrote: > Hi Amos, > > I kinda solved the problem (Thanks to you!!!) > All what was needed is to peek the important domains in step2 in order not > to cause them harm and bump everything else in step3. In this case I'm able > to read the dns names in the redi