Hi Christos, Firstly, thanks so much for your prompt responses. My ICAP server is listening on port 1344. I tried telnet to the box with port 1344 and it works fine. Also both Squid and ICAP server (Anti-Virus engine using ICAP protocol) sits on the same machine, but it still persists. Can you provide me with some more details to examine the Squid/ICAP negotiation? -----Original Message----- From: Christos Tsantilas [mailto:christos@xxxxxxxxxxxx] Sent: Tuesday, September 11, 2007 1:45 PM To: Shailesh Mishra Cc: squid-users@xxxxxxxxxxxxxxx Subject: RE: Configuring ICAP with Squid 3.0 Pre7 Hi Shailesh, The squid icap client before start using an ICAP server sends an OPTIONS request to this server to retrieve some information about this server (eg if previews supported, which file types must send etc). If the server does not respond correctly, the squid icap client will not use this ICAP service. So the line in your cache.log file says that something goes wrong in OPTIONS request send by squid icap client. Is your ICAP server listens to port 1344? Are you able to connect to the ICAP server on port 1344 from your squid machine (eg using a "telnet redhat4up4.sse.com 1344" )? If all the above are OK, maybe you can use tcpdump or wireshark to examine the squid/ICAP negotiation...... Regards, Christos > Also when I verified the cache.log file it says "2007/09/11 12:48:26| > essential ICAP service is down after an options fetch failu > re: icap://redhat4up4.sse.com:1344/respmod [down,!opt]". > > Regards, > Shailesh >
