ICAP error when filtering HTTP(S) response headers

UPDATE1: Please first of all check if your license is not expired. If you are using trial license please note it expired on March. 1, 2015. Visit http://quintolabs.com/licensing.php to get a new license.

UPDATE: bug is already fixed in version 4.0 of Diladele Web Safety – download at http://quintolabs.com/download.php.

Current stable version of Diladele Web Safety 3.4 has an unpleasant bug, when you have configured any of header only response filtering modules (content type blocking, file name or file type blocking and content charsets) Squid *may* mark qproxyd ICAP server as inactive. Users of proxy will then see the ‘ICAP server is failed’ error. The reason for this is incorrect ICAP response generated by qlproxyd daemon. The squid’s cache.log usually contains lines like essential ICAP service is suspended: icap://127.0.0.1:1344/respmod [down,susp,fail11].

If you have this issue please add icap_service_failure_limit -1 to your squid.conf.
We are currently trying to resolve this bug. Those interested may follow the bug fixing in https://github.com/ra-at-diladele-com/qlproxy_external/issues/676.

Sorry for the mess,
Diladele Dev Team

About sichent

sichent
This entry was posted in Linux. Bookmark the permalink.

One Response to ICAP error when filtering HTTP(S) response headers

  1. Pingback: qlproxyd crash during daemonize resulting in ICAP error | sichent

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s