Re: [squid-users] squid 3.2 intercept and upstream proxy not working

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 09 Aug 2012 13:47:34 +1200

On 09.08.2012 12:32, Eliezer Croitoru wrote:
> On 8/9/2012 2:16 AM, Amos Jeffries wrote:
>>
>> Releases 3.2.0.14->3.2.0.18 have a standing block preventing
>> requests
>> with conflicting destination IP and destination domain name being
>> passed
>> to peers.
>>
>> Release 3.2.0.19 loosens that block to allow it, but only if the
>> clients
>> original destination IP (ORIGINAL_DST) is non-contactable by the
>> proxy.
>>
>> BUT, ... checking your config file there is a bigger problem, and a
>> relatively large amount of useless ACL checks ...
> and let say i want to loosen it a bit more?

How much more?
  to relay known dangerous traffic to peers as if it were safe?
  or just to obey never_direct?

Amos
Received on Thu Aug 09 2012 - 01:47:38 MDT

This archive was generated by hypermail 2.2.0 : Fri Aug 10 2012 - 12:00:02 MDT