Hi Christos, I guess that there is a misconfiguration with my ICAP server I'm working on this.
Have you tried a configuration like this? It seems that service_3 will never be actived. icap_service service_1 reqmod_precache 0 icap://127.0.0.1:1344/wwreqmod icap_service service_2 respmod_precache 0 icap://127.0.0.1:1344/wwrespmod icap_service service_3 respmod_precache 0 icap://172.1.1.16:1344/respmod icap_class filtro_url service_1 service_2 service_3 icap_access filtro_url allow all Thanks, Thiago Cruz On 9/20/07, Christos Tsantilas <[EMAIL PROTECTED]> wrote: > Hi, > Works very well for me. How are you testing it? > Maybe the problem is repeated ICAP service failures. In this case squid > stops using the service. > > if you change the line: > icap_service service_2 respmod_precache 0 ..... > to > icap_service service_2 respmod_precache 1 ..... > > What are you seeing? > > The squid bugzilla is here: > http://www.squid-cache.org/bugs/ > > Regards, > Christos > > > Thiago Cruz wrote: > > Hi all, > > > > I was testing Squid 3.0.PRE6-20070718 and the ICAP protocol was working > > fine. I've updated to 3.0.PRE7-20070919 and squid stop sending Respmod, > > although the Reqmod is ok, follow my conf: > > > > icap_service service_1 reqmod_precache 0 icap://127.0.0.1:1344/wwreqmod > > icap_service service_2 respmod_precache 0 icap://127.0.0.1:1344/wwrespmod > > icap_class filtro_url service_1 service_2 > > icap_access filtro_url allow all > > > > I've tracked the connection and I can see ICAP server answering his > Methods: > > > > OPTIONS icap://127.0.0.1:1344/wwreqmod ICAP/1.0 > > Host: 127.0.0.1:1344 > > > > ICAP/1.0 200 OK > > Allow: 204 > > Encapsulated: null-body=0 > > ISTAG: "001-000-000003" > > Max-Connections: 50 > > Methods: REQMOD, RESPMOD, PROFILE, CERTVERIFY > > Options-TTL: 300 > > Preview: 30 > > Service: Webwasher 6.5.2.2676 (WW 6.5) > > Service-ID: ww > > Transfer-Preview: * > > X-Include: X-Authenticated-Groups,X-Authenticated-User,X-Client-IP > > > > > > Bugzilla? > > > > Thanks, > > Thiago Cruz > > > >
