Simplified the code by removing a local variable completely.

This makes the code flow more obvious and reacts on the return
code properly, even if the code acted the same way before.

When multi interface is used, the SSL handshake is no longer
blocking when GnuTLS is used.

The recent overhaul of the SSL recv function made this treat a
zero returned from gnutls_record_recv() as an error, and this
caused our HTTPS test cases to fail. We leave it to upper layer
code to detect if an EOF is a problem or not.

On some ancient distributions such as RHEL-3, <gssapi/gssapi_krb5.h> needs
to be processed after <gssapi/gssapi.h>, but does not include it itself.
This patch checks for <gssapi/gssapi.h> first and then includes it
in the test for <gssapi/gssapi_krb5.h>, resolving the problem.

Without the patch, <gssapi/gssapi_krb5.h> is "present but cannot be
compiled".

No resolver anymore needs to use AI_CANONNAME and do reverse
lookups.  We should work hard to avoid having code that relies on
it.

This code would previously use dns_entry->addr->ai_canonname
instead of the given host name, which caused us grief and
problems since not all our resolver options do the reverse lookup
and I would also guess that it caused problems with KRB5/GSS with
virtual name-based hosts. Now the host name from the URL is used.

Based on a patch from the FreeBSD ports by Peter Pentchev.

As reported in bug report #2987196, the code for ipv6 already did
the setting of this bit correctly so we copied that logic into
the Curl_ipv4_resolve_r() function as well. KRB code is the only
code we know that might need the cannonical name so only resolve
it for such requests!

Signed-off-by: Tor Arntsen <tor@spacetec.no>

no need to create a var - lets just return the status var itself.

The section that describes how to work with timeouts was
misleading and could easily trick users to use the wrong API.

c-ares has had its own URL for a while and we should point
people to that. It also works with IPv6 since a long time.

curl_multi_timeout(3) is simply the wrong function to use
if you're using the multi_socket API and this document now
states this pretty clearly to help guiding users.