Leonardo Rodrigues Magalhães wrote:
Henrik Nordstrom escreveu:
Not sure if it's a bug or a feature..
But it's very easy to live with. Just set up another http_port for the
transparent interception.
Yeah .... i also dont know if this is a bug or a feature :) And it's
easy to live with, i agree with that.
Anyway, i think this should be investigated and, if declared as
feature and not bug, it should be at least documented. Actual
'transparent' option documentation says nothing about authentication
mechanisms completly stop working as it seems to happen.
I've seen this at close quarters recently. It worked in 2.5 because
there was only one port. In 3.0 and later it turns off several
components doing expensive network or kernel lookups, not just
authentication.
The fix here is in the documentation as you point out.
Amos
--
Please use Squid 2.6.STABLE20 or 3.0.STABLE6
