squid3 and SpamBayes
I'm testing squid3 to see if I can upgrade from squid2, primarily for the c-icap/squidclamav capabilities. The system is Debian Wheezy fully updated. I've already found workarounds for the ipv6 problems that plague Debian's squid3 ver. 3.1.19.
The one problem I have been unable to circumvent is accessing the web interface of SpamBayes pop3 proxy. SpamBayes resides on a different host than squid3, but both are behind the firewall. When attempting to access SpamBayes web interface, the squid error page appears stating "zero sized reply". This occurs regardless of whether I use the host's alias, its real hostname, or its IP address. The port on which Spambayes' web interface runs is a squid safe port. Other services with web interfaces on the same host as SpamBayes(e.g. CUPS), are readily accessible. If SpamBayes is installed on the squid3 host, the web interface is then accessible.
So, with all this trial and error, the problem appears to be SpamBayes when installed on a host remote to squid3. All other permutations work. I do not have this problem with squid2.
Can any squid expert diagnose the problem here? Any help is greatly appreciated.
|