Re: [squid-users] dansguardian, squid, shorewall

On 9 Jan 2008 at 11:50, Amos Jeffries wrote:

> Richard Pyne wrote:
> > Well, I solved my problem for now, I went back to squid 2.6, made NO
> > configuration changes, and everything is working fine. So much for
> > "improved" versions.
>
> Are you sure 2.6 accepted those config lines? did you mean 2.5 works
> with that 2.5 syntax?
>
> In 2.6 and 3.x the accelerator host stuff has been replaced by a single
> simple:
>
> http_port 80 accel vhost
>
> As stated in the 2.6 release notes:
> http://www.squid-cache.org/Versions/v2/2.6/RELEASENOTES.html#s2
>
> Amos
>

It did not accept the config lines, but even without them it works with
DansGuardian whre squid 3.0 does not while using EXACTLY the same
configuration with 2.6 and 3.0.

--Richard

> >
> > --Richard
> >
> > On 8 Jan 2008 at 10:08, Richard Pyne wrote:
> >
> >> On 7 Jan 2008 at 23:43, Amos Jeffries wrote:
> >>
> >>> Adrian Chadd wrote:
> >>>> Have you configured the http_port with 'transparent' ?
> >>>>
> >>> I think the problem here is that its *dansguardian* being redirected to
> >>> not squid. The transparent features of squid will not work when there is
> >>> no redirection, ie between dansguardian and squid.
> >> After many hours of searching and reading, it looks like the real problem
> >> is that squid v3 does not support:
> >>
> >> httpd_accel_host virtual
> >> httpd_accel_port 80
> >> httpd_accel_with_proxy on
> >> httpd_accel_uses_host_header on
> >>
> >> which everything I can find on this problem says are necessary for
> >> DansGuardian + squid configuration.
> >>
> >> I have not been able to find anything to indicate what configuration
> >> directives in squid 3 replace this functionality or if such even exists.
>
>
>
> >>
> >> Any help or direction will be greatly appreciated.
> >>
> >> --Richard
Received on Tue Jan 08 2008 - 16:07:57 MST