On Thu, 2008-04-10 at 12:16 +0200, Davide Meloni wrote: > 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 Please double check that the X-Authenticated-User header was in the HTTP header encapsulated in the ICAP request and not in the ICAP header itself. > 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? That patch was not committed. IIRC, there were two conflicting implementations or reviews of this feature and the folks either failed to reconcile their differences or abandoned the work. The header of the patch you found says it is not ready for merging... However, if the X-Authenticated-User header is in the HTTP message, then the patch you found is irrelevant as it only affects the ICAP headers. Please double check and we will go from there. Thank you, Alex.
