Hi,
Looks like I was mistaken, this is broken in squid 3.2.0.13 as well. I
believe this is the behavior seen in:
http://bugs.squid-cache.org/show_bug.cgi?id=3437 (digest causes auth
loop between browser and squid)
http://bugs.squid-cache.org/show_bug.cgi?id=3186 (digest auth is
incorrectly cached)
I believe #3437 is a side-effect of #3186
STR: (using cURL)
1. Configure squid to use digest auth
2. Start squid
3. export http_proxy=http://user:pass@host:port
4. curl -I --proxy-digest sydonis.com
5. Works as expected
6. export http_proxy=http://user:wrongpass@host:port
7. curl -I --proxy-digest sydonis.com
8. Unexpectedly works.
9. Restart squid
10. curl -I --proxy-digest sydonis.com
11. Fails as expected
12. export http_proxy=http://user:pass@host:port
13. curl -I --proxy-digest sydonis.com
14. Fails with 50 redirects (cURLs max)
I'll try earlier versions of 3.2.0.x to see if there's a regression,
then I'll try the fix suggested in #3186.
Regards,
--Will
Received on Sat Feb 04 2012 - 18:42:09 MST
This archive was generated by hypermail 2.2.0 : Sun Feb 05 2012 - 12:00:11 MST