On 2014-03-18 05:06, Alan wrote:
On Mon, Feb 3, 2014 at 4:18 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx>
wrote:
* Fix external_acl_type async loop failures
This issue shows up as extra failed authentication checks if the
external ACL uses %LOGIN format code and credentials are not already
known. This can have nasty side effects when combined with NTLM in
older
3.4 releases.
Will this be backported to the 3.3 series? How bad is it when using
Kerberos instead of NTLM?
I can't update to 3.4 because of the cpu usage problem described in
the thread titled "squid 3.4. uses 100% cpu with ntlm_auth".
Would it be too optimistic to think that this fix solves the cpu usage
problem?
Doubtful. This was a regression fix for a bug added in the 3.4.0.1 ACL
redesign as far as I can tell.
AMos
