Is this committed to SquidGuard and updated in IPCop? If so, good news.
Breaking Google (and many others) is a pretty serious bug(1).
For what it's worth, we've moved to writing squid acls in include.acl.
There's no web ui but the rules and documentation are now in the same file
and thus kept in sync much more accurately. Entire paragraphs of doc. right
beside the implementation. Performance is probably worse but it's enough for
us. Overall, it feels like an upgrade.
(1) I'm aware (now) that SquidGuard is shipped but "disabled" by its absence
from the menu. I just didn't notice at the time when migrating config files
in the shell.
> -----Message d'origine-----
> De : Gilles Espinasse [mailto:g.esp@...]
> Envoyé : 8 mai 2013 05:31
> À : Pierre Pelletier
> Cc : ipcop-user@...
> Objet : Re: [IPCop-user] squidGuard broken for urls containing "%0a"?
> ----- Mail original -----
> > De: "Pierre Pelletier" <pierre.pelletier@...>
> > À: ipcop-user@...
> > Envoyé: Lundi 14 Mai 2012 21:12:23
> > Objet: Re: [IPCop-user] squidGuard broken for urls containing "%0a"?
> > >
> > > Pierre Pelletier wrote:
> > > > Is anybody else having a problem with squidGuard on IPCop v2.04
> where urls
> > > > containing "%0a" produce 2 answers, as if the encoded newline was
> > > > but not re-encoded?
> > [snip examples]
> Almost a year passed and I find a solution for that issue.
> I find the fix for that issue in debian patch set for squidguard-1.5.
> So I applied all debian patches plus a few warning fixes.
> This has been commited in our tree just now.