In doing some dev work I see a situation where squid gets into an infinite loop with the browser. The situation: 1) Browser attempts digest authentication against squid (running with a custom auth helper) 2) auth helper fails user authentication 3) I believe squid caches the authentication failure 4) Browser requests a page using the above authentication 5) Squid replies with 407 - authentication required 6) INFINITE LOOP: (Browser retries request : squid replies with 407) The above loop running locally can rack up a meg of data transfer in just seconds. I remember dealing with this issue some time back in some other work and just don't recall what I did about it. I'm running a custom auth helper, log daemon, and url rewrite helper.
