Carrying on from commit 1102561, added VC9 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
Given that we presently support "auth" and not "auth-int" or "auth-conf" for native challenge-response messages, added client side validation of the quality-of-protection options from the server's challenge message.
... the recent MSVC project files added by Steve Holme
Bug: http://curl.haxx.se/mail/lib-2014-04/0063.html Reported-by: Jeroen Koekkoek
To avoid urldata.h being included from the header file or that the source file has the correct include order as highlighted by one of the auto builds recently.
warning: no previous prototype for 'Curl_sasl_create_digest_md5_message'
warning: 'sasl_digest_get_key_value' defined but not used
* Added comments to SSPI NTLM message generation * Added comments to native DIGEST-MD5 code * Removed redundant identity pointer
When CURL_DISABLE_CRYPTO_AUTH is defined the DIGEST-MD5 code should not be included, regardless of whether USE__WINDOWS_SSPI is defined or not. This is indicated by the definition of USE_HTTP_NEGOTIATE and USE_NTLM in curl_setup.h.
* Added information regarding the February 2003 Platform SDK for VC6 * Updated the introduction to be similar to the IDE projects README
Added a more thorough version of the VC8 project files that exist in the "vs" folder with the intention to add support for other versions of Visual Studio. These files support side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
And clarify for curl that --proxy-header now must be used for headers that are meant for a proxy, and they will not be included if the request is not for a proxy.
Updated the docs to clarify and the code accordingly, with test 1528 to verify: When CURLHEADER_SEPARATE is set and libcurl is asked to send a request to a proxy but it isn't CONNECT, then _both_ header lists (CURLOPT_HTTPHEADER and CURLOPT_PROXYHEADER) will be used since the single request is then made for both the proxy and the server.
... and sorted the list