On Oct 14, 2012, at 4:28 PM, Cédric Deltheil <cedric_at_moodstocks.com> wrote:

> Le 15 oct. 2012 à 00:15, Joe Mason a écrit :
>
>> I just discovered this myself, and I'm working on a test case.
>
> I would be pleased to get some more details about how to reproduce this problem.
>
> On my side, I've precisely a bunch of code that re-uses curl handles with Digest authentication so I gave the 7.28.0 version a try.
>
> I've just bumped from libcurl 7.25.0 to 7.28.0 but I cannot reproduce Nick's problem (steps 1 to 10).

Well, I just tried to see if I could reproduce it with the command line client. I was unable to reproduce the problem when doing something like this:

% src/curl --digest -v -u john_doe {https://example.net/someplace/,https://example.net/someplace-else/}

But I was able to reproduce the problem when I did this instead:

% src/curl --anyauth -v -u john_doe {https://example.net/someplace/,https://example.net/someplace-else/}

(URLs changed because I found this problem while accessing a private server.)

So it appears that limiting authentication choices to digest only works around the problem. I also tested this with OS X's built-in curl tool, which is at version 7.24 under Mountain Lion, and it does not have this problem.

I hope this helps resolve the issue. And I realize how frustrating it is when a bug-fix ends up causing a regression…

Nick Zitzmann
<http://www.chronosnet.com/>

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-10-15