Here we are, 6 months later, and nothing has changed. 15.10 ships with
the same incompatible Squid 3.3.8 and squidGuard 1.5-4. Unbelievable.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Is there going to be some resolution to this or will we have to wait
until 15.10?? Frankly, I find it bizarre that they're packaging an
ancient version of squid3 with a bleeding-edge version of squidGuard. I
would think that using Ubuntu Server as a web proxy would be a fairly
common thing, and
Well, either squid has to move up to 3.4+ which you said is a non-
starter, or squidGuard has to move back down to 1.5-2 which the Debian
guys aren't likely to do. So that leaves us nowhere.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I emailed the maintainer and received this reply:
Can you please confirm that the squidGuard 1.5-4 will or won't work with
the shipping squid 3.3.8?
This is right. The problem was, that squid3 have changed its redirector
protocol several times. Until squid3 3.3.x older protocols were allowed.
Public bug reported:
I had a working config on Ubuntu 14.10 Server with Squid 3.3.8 and
squidGuard 1.5-2. I spun up a 15.04 Server box and installed both and
copied over the .conf files. Squid works like a charm. squidGuard
fails with:
2015/04/23 16:15:44 kid1| ERROR: URL-rewrite produces
I should note that 14.10 shipped with squid 3.3.8 and squidGuard 1.5-2.
15.04 ships with squid 3.3.8 but squidGuard 1.5-4. The 1.5-4 changelog
shows they made some changes to support squid 3.4 and how that was the
new base version. No wonder 1.5-4 doesn't work with 3.3.8.
From Launchpad:
