Davide Meloni wrote:
Hi all,
I'm trying to configure Squid3.0.STABLE1 for talk to a content
filtering service in ICAP, but my content filter engine cannot apply
the correct users's group policy.
Sniffing with wireshark I found this difference in HTTP Header between
Squid and a third party product (this last work fine):
Squid:
X-Authenticated-User: test\r\n
Third party:
X-Authenticated-User:
LDAP://myldapserver:389/uid=test,ou=People,o=myoffice,dc=mycompany,dc=global\r\n
Looking in ML archive I found a thread treating the solution to my problem:
http://www.squid-cache.org/mail-archive/squid-dev/200611/0066.html
but I can't find the configuration's parameters treated in the patch
that was attached to the message above.
Can anyone here tell me if I've lost something in the configuration
file or if the patch was not included in the official release or if it
will be in the next or whatever?
It appears that the patch never made it into the official sources of
squid (any version).
The closest present is the "icap_send_client_username" and related
options. Which don't appear to do LDAP encoding or anything similar.
Alex did the ICAP work in squid-3, if he does not reply to this thread
in the next day or so with an answer you should try contacting him.
Amos
--
Please use Squid 2.6.STABLE19 or 3.0.STABLE4
