Howdy Folks,

We currently have two outstanding connectivity issues with libCurl and BOINC. We have a patch that works around a SOCKS proxy connection problem which we are using with success against the 7.15.3 source tree.

Here is the patch description for the SOCKS patch:
-----
First is with sock5 proxy, on Windows libcurl connects, but before the connection is made libcurl writes to the socket. That produces an error and the socket is closed. Libcurl needs to wait until the connection is complete before writing to the socket.

Attached is a patch (url_c.patch) that addresses the connect issue, but it blocks during the connect while the sock protocol is being handled. Not good since we're using the multi interface.
-----

We have another problem involving NTLM authentication against a proxy server with an HTTP POST request. I have included some trace files

Here is the problem description for it:
-----
Data we're sending is 4556 bytes, after 1460 bytes are sent, the proxy server responds with a 407, more authentication needed. Libcurl proceeds to send the rest of the buffer, then the header for the next stage of the authentication. Not good.

We're using CURLOPT_READFUNCTION with CURLOPT_READDATA and CURLOPT_IOCTLFUNCTION callbacks.
-----

I can provide access to a VM with Windows installed and a proxy server with NTLM authentication capabilities. Are their any additional tools you would need? The NTLM authentication problem happens with our current stable release of our software and the latest dev release as well. Both can be found http://boinc.berkeley.edu/download_all.php?dev=1.

Any help you all can provide is greatly appricated. Thanks in advance.

----- Rom