Setting CURLMOPT_PIPELINING on my CURLM handle causes problems for me when I use digest authentication (7.26.0, C++, Win64).

I get a CURLMSG_DONE message which reports CURLE_OK but curl_easy_getinfo CURLINFO_RESPONSE_CODE gives me 0 and the downloaded buffer has the boilerplate 401 anauthroized HTTP in it over and over as if all the pipelined requests failed and put their results in the same message.

I've tested extensively without CURLMOPT_PIPELINING and it works like a dream.
I've also tested extensively with CURLMOPT_PIPELINING on a server without any authentication which also works.

It could be related to the fact that CURLAUTH_DIGEST which requires an exchange with the server before getting content.

I was wondering if I could defer setting CURLMOPT_PIPELINING until the 1st request through the CURLM handle was complete but I can't be sure when I was reconnected to disable until a request had gone through.

Any advice? I suspect I'm asking for too much. I also suspect that doing basic password auth might just work because you can include it in the initial request.

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