... as we're HTTPS on the main site now, there's no point in that
extra step

closesocket => close_socket
Winsock already has the former.

Bug: https://curl.haxx.se/mail/lib-2016-02/0016.html

Bug: https://curl.haxx.se/mail/lib-2016-02/0017.html

Closes #632

.. also warn about letting the server pick the filename.

Reported-by: Bernard Spil

Current FAQ didn't make it clear where the main repo is.

Closes #612

The CURLOPT_SSH_PUBLIC_KEYFILE option has been documented to handle
empty strings specially since curl-7_25_0-31-g05a443a but the behavior
was unintentionally removed in curl-7_38_0-47-gfa7d04f.

This commit restores the original behavior and clarifies it in the
documentation that NULL and "" have both the same meaning when passed
to CURLOPT_SSH_PUBLIC_KEYFILE.

Bug: http://curl.haxx.se/mail/lib-2016-01/0072.html

Closes #514

- Add to both curl_global_init.3 and libcurl.3 the caveat for Windows
that initializing libcurl via a DLL's DllMain or static initializer
could cause a deadlock.

Bug: https://github.com/bagder/curl/issues/586


Reported-by:  <marc-groundctl@users.noreply.github.com>

This is the new command line option to set the value for the existing
libcurl option CURLOPT_EXPECT_100_TIMEOUT_MS

... and stick to 1.1 for HTTP. This is in line with what browsers do and
should have very little risk.