Qlproxy ICAP Protocol Error?

Rafael

unread,

Oct 3, 2011, 3:16:29 AM10/3/11

to quintolabs-content-se...@googlegroups.com

Having the last 1.4.0 edition of QuintoLabs Content Security installed on your Squid proxy you may experience the “ICAP Protocol error” from your browser. The problem here is qlproxy crushes suddenly while doing content filtering of ICAP traffic coming from Squid. And when Squid can not contact the ICAP server it gives users the “ICAP protocol error” page.

We deeply apologize for the error. Crush investigation revealed a problem in AdBlock module… it has been fixed and new build of qlproxy is going to be released today (3rd October 2011). For now it is recommended to set the icap_enable directive to off in your Squid server and restart it.

Sorry so much,

QuintoLabs Team

Rafael

unread,

Oct 3, 2011, 3:35:59 AM10/3/11

to quintolabs-content-se...@googlegroups.com

You may also disable adblock module BTW.

Victor Krot

unread,

May 12, 2014, 4:42:45 AM5/12/14

to quintolabs-content-se...@googlegroups.com

I have same problem since april - too frequent "ICAP protocol error" - Disabling AdBlock not helping - only restarting.

How can I fix it?

Version 3.2.0.4CAF

Rafael

unread,

May 12, 2014, 4:50:34 AM5/12/14

to quintolabs-content-se...@googlegroups.com

No no this should not be related to adblock anymore,

Victor - what exactly is printed on the blocked page? This *may be related to squid unable to contact icap server because it ran out of file descriptors, what exactly you restart - squid or qlproxy?

And cache.log of squid usually shows the file descriptor issue - could you share it here or at sup...@diladele.com?

Raf

Reply all

Reply to author

Forward