Re: [squid-users] Question about cache_peer, squid 3.2 Bug ?

> Please update to the stable release 3.2.1.
>
> With 3.2 you have "debug_options 11,2" which will produce a full
> trace
> of HTTP headers in cache.log which will greatly help understanding
> why
> the 502 occured. (careful about size and confidential info if this is
> used on a production machine)
>
> I also suggest using the squid format for access.log, it includes
> details such as the IP of the server which that 502 is related to.
>
> Amos
>
>

Ok I found where is the problem

I tried with PASSTHRU and all seems work
cache_peer 10.x.x.x parent 3128 0 no-query login=PASSTHRU proxy-only no-digest no-netdb-exchange

So the problem was with =PASS, like this bug

Tue 2012-08-28 21:36:29 -0600 Amos Jeffries Regression: login=PASS send no credentials when none available.

So now, The strange behavior was for users without problem, they navigates through squid although there is a bug
No problem with 3.2.1 thank
Received on Mon Sep 17 2012 - 13:52:50 MDT