Hi Christos, As you mentioned in the previous mail "Maybe 201 responses make sense in the case the content returned to the ICAP client is not the original but created internally by ICAP server. It can be handled exactly as the 200 responses by the squid ICAP client" . You are right here . As Symantec Scan Engine 5.0 and later sends the response as 201 always for a modified request inside ICAP server ( infected files getting deleted or repaired) . The user when requesting for a file ends up with getting an error which says " ICAP Protocol Error" . Is this expected to be fixed in near future? Regards, Shailesh -----Original Message----- From: Christos Tsantilas [mailto:christos@xxxxxxxxxxxx] Sent: Monday, September 17, 2007 5:16 PM To: Shailesh Mishra Cc: Henrik Nordstrom; squid-users@xxxxxxxxxxxxxxx Subject: RE: Squid 3.0 ICAP response codes. Hi, > Hi Henrik, > > For a AV scenario where any anti-virus solution scans a repairable file > and repairs it , the file is not returned to the client as the ICAP > response for this case is 201 which is not understood by squid. Whereas it > works fine if AV solution is configured for not repairing the file but > just to scan it. > > AV server here uses response code 201 I think the way the 201 responses handled by your ICAP server is different than the case described here: http://cvs.squid-cache.org/mail-archive/squid-users/200508/0690.html Are you referring to the same ICAP server? Reading the ICAP and HTTP rfcs I am confused.... Henrik has right, it is not so clear what should contain an ICAP 201 response..... Regards, Christos
