I'm working with a patch I did for that purpose, only thing is that
something I did caused a segv when it does a reconfig, which is why I
haven't committed to the icap branch.
_J
>>> "Westerhold, Axel" <Axel.Westerhold@dts.de> 11/21/06 12:54 PM >>>
Hi All,
I will have a look at the squid3 but I will need to modify it a little
bit
so that I can split the Domain Part of the Username to make the
webwasher
happy on ist AD samaccount queries. From what I can see it should be
easy
enough to get this done inlcuding a way to enable/disable this feature
(like
the one I did for 2.x).
Also, I just shipped a 2.6 ICAP Patched Squid in a cluster setup to a
customer with 1000 Users. This Pilot Installation will get me a good
feeling
how stable 2.6 works.
Regards,
Axel
Am 20.11.2006 22:57 Uhr schrieb "Tsantilas Christos" unter
<chtsanti@users.sourceforge.net>:
> Hi all,
> The reported problems exists and are not webwasher related, exists
for
> every icap server.
>
> Axel's solutions causes crashes to squid in some cases. I think it
> happens when http client closes the connection before the connection
to
> the icap server closed. I am not sure it needs more debugging.
> I am planning to give some more time...
>
> However, the squid3 with icap client is more stable than squid-26
with
> icap patch. I think the squid3 has only 2-3 bugs before the release.
> My opinion is that it does not make sense for someone to spend time
in
> squid26 icap client, it is good for testing and development but only
> that .....
>
> Regards,
> Christos
>
> Westerhold, Axel wrote:
>> Well,
>>
>> as I have a customer waiting for a fix I will just go with my
modification
>> and will try to pin down the real fault when I have some free time
>> available. Setting the major version the way I do should not have a
real
>> impact at least I can't see one right now on my test system.
>>
>> Regards,
>> Axel
>>
>>
>>
>
Received on Tue Nov 21 2006 - 11:01:59 MST
This archive was generated by hypermail pre-2.1.9 : Wed Nov 29 2006 - 12:00:05 MST