Re: [squid-users] upgrade to squid 3.0 breaking existing authentication module

frigoris.ma_at_gmail.com wrote:
> Dear Henrik:
>
> Thanks for the reply.I tried fixing the uid/gid and the authenticator
> processed no longer crashed.
>
> However, squid never seemed to be using them to do the authentication.
> The ACL and http_access parts of my configuration file are ported from
> the old config which actually worked.
>
> These parts of the config file are largely identical to the default
> one, except for the one ACL
> of "proxy_auth" and the corresponding http_access entry.
>
> The result is that squid never really authenticate a user matching the
> proxy_auth ACL. If one surfs the web via my cache, he gets an "Access
> Denied" error page from squid, and there are no prompt for entering
> username and password before the error page is delivered. I tried the
> PAM authenticator and the result was similar.
>
> I guess I'll have to downgrade to 2.6 and do some comparisons to find
> out the problem.

If you would care to share the ACL and http_access lists we may be able
to help.

I'd also advise going up to stable 4+ as there are a number of small
bugs that have been found and fixed since stable 2.

Amos

-- 
Please use Squid 2.6.STABLE20 or 3.0.STABLE5