4 more bugfixes, 3 more contributors

Synced the output to the same short form as we now use for
Windows SSL (WinSSL).

Previously the curl_multi interface would freeze if darwinssl was
enabled and at least one of the handles tried to connect to a Web site
using HTTPS. Removed the "wouldblock" state darwinssl was using because
I figured out a solution for our "would block but in which direction?"
dilemma.

Reported by: Santhana Todatry

DragonFly uses milliseconds, while our API and Linux use full seconds.

Reported by: John Marino
Bug: http://curl.haxx.se/bug/view.cgi?id=3546257

Bug: https://bugzilla.redhat.com/676596

... and orig_isatty which caused --silent to be entirely ignored in case
the standard output was redirected to a file!

The clean-local hook needed some polish to make sure make distclean
works. Added comment describing why.

Previous fix didnt work on Linux ...

Replaced the Windows real path from mount hack with a more
reliable and simpler hack: the MSYS shell has a builtin pwd
which understands a -W option which does convertion to Windows
paths. Tested and confirmed that this works on all MSYS versions
I have back to a 3 year old one.

1) the check for winssl needs to come before nss check
2) the SSL checks must begin with a new if or else we will
never find any SSL lib with MinGW.

This is a MSYS/MinGW-only warning; full warning text is:
Use of uninitialized value in numeric gt (>) at ../../curl/tests/runtests.pl line 2227.

Fixed 6 bugs, added 3 contributors

In many states the easy_conn pointer is referenced and just assumed to
be working. This is an added extra check since analyzing indicates
there's a risk we can end up in these states with a NULL pointer there.

It should return PARAM_NO_MEM if the strdup fails. Spotted by
clang-analyzer

Spotted by clang-analyzer

Spotted by clang-analyzer. The return code was never checked, just
stored.

va_end() needs to be used after va_start() and we don't normally use
Curl_ prefixes for purely static functions.

This avoids false positives from clang's scan-build.

Test 1409 and 1410 verifies the stricter numeric option parser
introduced the other day in commit f2b6ebed.

I made "connmon" not get initialized properly before use, and I use the
big hammer and make sure we always clear the entire struct to avoid any
problem like this in the future.

Two commits ago, we fixed a bug where the connction would be closed
prematurely after a HEAD. Now I added connection-monitor to test 48 and
added a second HEAD and make sure that both are sent over the same
connection.

This triggered a failure before the bug fix and now works. Will help us
avoid a future regression of this kind.

This makes verifying easier and makes us more sure curl closes the
connection only at the correct point in time. Adjusted test 206 and 1008
accordingly and updated the docs for it.

A HEAD response has no body length and gets the headers like the
corresponding GET would so it should not get closed after the response
based on the same rules. This mistake caused connections that did HEAD
to get closed too often without a valid reason.

Bug: http://curl.haxx.se/bug/view.cgi?id=3542731
Reported by: Eelco Dolstra