Re: [squid-users] external_acl_type not reliable after upgrade from 2.7 to 3.1.20

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Fri, 11 Oct 2013 13:10:04 +1300

On 11/10/2013 3:48 a.m., Thomas Stegbauer wrote:
> On 10.10.2013 06:31, Amos Jeffries wrote:
>> On 10/10/2013 12:33 p.m., Thomas Stegbauer wrote:
>>> hi,
>>> ...
>>> The acl is configured like this:
>>> external_acl_type phpauthscript protocol=2.5 children=100 ttl=0
>>> negative_ttl=0 %SRC /etc/squid3/authscript
>>>
>>> best regards
>>> thomas
>>
>> Please try adding the option "ipv4" to that configuration line for
>> squid 3.1.6 and 3.1.20 in Debian.
>>
>> Amos
> Hi Amos,
>
> external_acl_type phpauthscript protocol=2.5 children=100 ttl=0 ipv4
> negative_ttl=0 %SRC /etc/squid3/authscript
>
> does not change the error, it still occures. mostly when there are
> more than one client.
> the authscript still does sometimes note geht the ip.
> where is here an IPv6 connection? the IP get sent via STDOUT to
> authscript.
>
> thomas

stdin/stdout/stderr can be connected to any type of backend socket.
Squid on some OS chooses to use TCP for them, which brings up the
default-IPv6 issues.

It might also be off-by-1 errors which have been found in 3.1/3.2 series
handling of the TTL. Are you able to try out a 3.3 release?

Amos
Received on Fri Oct 11 2013 - 00:10:15 MDT

This archive was generated by hypermail 2.2.0 : Fri Oct 11 2013 - 12:00:04 MDT