Alex Rousskov wrote:
FWIW, the above drweb behavior is compliant with ICAP. Conection: keep-alive
does not (and cannot) guarantee that the connection will remain open after
the ICAP response is sent.
OK.
Not using persistent connections with a given ICAP server would also be compliant with ICAP. Persistent connections are optional.
I made a first implementation uisng an extra option to icap_service option in squid.conf:
icap_service servicename vectoring_point bypass service_url [keep_alive=on|off]
But after that I spent time to correct some reported bugs and I did not finish it.
I must look on it again and make some clean-ups.
Have you tried asking drweb folks whether there is something Squid can do to prevent them from closing the connection?
No I did not.
But the DRweb team had post a patch to squid mailing list (http://www.mail-archive.com/[email protected]/msg02325.html)
for squid-icap in which had modify the code to always closing the connection.
So, I believe that drweb-icapd requires closing the connection.
Regards, Christos
