Re: [squid-users] icap_access and external_acl does not work

2004-10-13 Thread Stephane DAVY
"http_access allow one_group", it is not enough to put http_access allow all I hope this helps -- Stephane DAVY <[EMAIL PROTECTED]>

[squid-users] Patch for load-balancing et HA in Squid-ICAP client

2004-10-04 Thread Stephane DAVY
patch should be applied against the latest tarball available here: > http://www.squid-cache.org/~wessels/squid-icap-2.5/ > > Dont' forget to run bootstrap.sh before configure > > Feedback is welcome at the following address: > [EMAIL PROTECTED] and of course on this ML >

Re: [squid-users] regarding the ICAP patch

2004-09-23 Thread Stephane DAVY
still remaining, in particular under high load, but I've never encounter this problem of connection refused. -- Stephane DAVY <[EMAIL PROTECTED]>

[squid-users] Squid-ICAP mailing list

2004-09-20 Thread Stephane DAVY
Hello, it seems that there is more and more interest for the ICAP part of Squid. A mailing list is also available for this topic: https://lists.sourceforge.net/lists/listinfo/icap-server-squidclient -- Stephane DAVY <[EMAIL PROTECTED]>

Re: [squid-users] ERR_ICAP_FAILURE

2004-09-15 Thread Stephane DAVY
27;ve already seen that, WebWasher returns an HTTP status line, not an ICAP one so the icap_client is quite confused with it. Is your WebWasher proxy activated? -- Stephane DAVY <[EMAIL PROTECTED]> --- configure.in 2004-09-15 14:42:57.0 +0200 +++ configure.in.new 2004-09-15 14:

Re: [squid-users] SQUID + LDAP HELP

2004-07-16 Thread Stephane DAVY
> external_acl_type AD_Group %LOGIN > /usr/lib/squid/squid_ldap_auth -b > cn=users,dc=dom1,dc=info,dc=co -D > cn=user1,cn=users,dc=dom1,dc=info,dc=co > -h 10.10.1.25 -w pass1 -S -f > "(&(cn=%u)(memberOf=cn=internet,cn=users,dc=dom1,dc=info,dc=co))" it seems that your external_acl definition is