Using stable squid and clamd. Upgrading squidclam-0.20 to squidclam-0.21 screwed up the proxy redirecting every request to the "infected" page. Clamd, squid and squidclam configuration remained the same. Downgrading to 0.20 solves the problem. Fortunatelly (unlike eaccelerator and mysql) the previous ebuild remained in the tree, so I could use it in the absence of an archived portage tree. The phenomena is clearly linked to the new version. No specific error messages can be seen in any of the system logs. Squid log shows only the necessary log signs of redirection. I have no clue on this behaviour. The clamd is accessible all the time on 127.0.0.1:3310. Other applications and the previous version of squidclam can communicate with it. Regards, Dw.
works for me, with default squidclam.conf and squid.conf settings recommended by pkg_postinst info messages: * THIS PACKAGE IS IN ITS EARLY DEVELOPMENT STAGE! * See http://squidclam.sourceforge.net/ for more info. echo einfo Add following lines to your squid.conf: einfo redirect_program /usr/bin/squidclam einfo redirect_children 15 * and this line to your acl list to prevent loops: * redirector_access deny localhost * Squid doesn't pass complete ssl urls to the redirector! * Therefore scanning them is pretty useless. * Add something like the following to avoid this and save bandwidth: * acl SSL_ports port 443 563 * redirector_access deny SSL_ports
*** Bug 137365 has been marked as a duplicate of this bug. ***
