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

From: Amos Jeffries <>
Date: Fri, 10 Aug 2012 19:35:41 +1200

On 10/08/2012 7:36 a.m., Davide Alberani wrote:
> On Thu, Aug 9, 2012 at 1:16 AM, Amos Jeffries <> wrote:
>>> I'm trying squid 3.2 (since I'll need some of the new features), but I'm
>>> having troubles using it in intercept mode, when used along with an
>>> upstream proxy.
>> Which 3.2 release number please? that matters a LOT.
> Pardon; it was a; I'll try with the latest version as soon
> as possible and I'll post the results.
>> BUT, ... checking your config file there is a bigger problem, and a
>> relatively large amount of useless ACL checks ...
> Thank you very much for all the hints about the configuration!
>> In 3.2 the default action when no cache_peer_access at all is configured, is
>> to attempt to use the peer.
> I see.

FYI: I'm having to bump out a new .20 package due to another issue. You
may wish to wait for that to improve the peer selection for interception

>> Maybe we have a bug in FIRSTUP_PARENT selection not checking the
>> cache_peer_access properly.
> I'll do some tests in the next days, and let you know the results.
> What's the best debug_options to use, to analyze the FIRSTUP_PARENT
> selection?

Hm,. most of this is not containing debug messages so its tricky.
Access Controls and peer selection levels would be best I think.

Received on Fri Aug 10 2012 - 07:35:56 MDT

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