[Slackbuilds-users] SquidGuard 1.4 vs. Squid 3.4 : patch for vanilla sources needed
hostmaster at slackonly.com
Sat May 2 06:48:45 UTC 2015
i have attached SquidGuard patch.
On 05/02/2015 09:33 AM, Niki Kovacs wrote:
> Le 02/05/2015 08:29, Niki Kovacs a écrit :
>> I'm using a combination of Squid and SquidGuard on my servers for web
>> filtering, which is the "industrial grade" solution usable in schools
>> and companies.
>> Up until recently, the combination worked well with Squid 3.3 and
>> SquidGuard 1.4. Unfortunately, the upgrade to Squid 3.4 broke something,
>> and SquidGuard doesn't work anymore.
>> I've googled a bit, and found out that SquidGuard 1.4 has to be patched
>> in order to work with Squid >= 3.4.
>> Now I just spent some time hunting down that mysterious patch, but I
>> failed, because all the patches are either distribution-specific
>> (FreeBSD, Arch, etc.) and they don't work with vanilla sources, or the
>> link to the original patch throws back a 404 error.
>> My guess is the SquidGuard application is quite badly maintained,
>> judging from their homepage displaying a forest of patches and
>> announcing a perpetual 1.5beta version for the last couple of years.
>> If anybody has an idea, that would be helpful.
> Some additional information. Here's the relevant bit from the
> SquidGuard mailing list. The URL to the included patch does not work.
> On Thursday, 13. March 2014 21:57:39 Ming Hou wrote:
> > Hi,
> > I have upgraded my squid proxy from 3.1.23 to 3.4.4 with squidGuard
> > For some reasons, the redirection from the result of squidGuard
> throws out
> > the 404 error. However, I switch back 3.1.23 and the issue goes away.
> > Any suggestion?
> please see this "bug" report:
> -> You need to patch squidguard to work with newer squid versions.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2619 bytes
Desc: not available
More information about the SlackBuilds-users