2 - properly escape certain letters within a DICT word to comply to the RFC2229

connects. The state machine was not reset properly so that subsequent
connects using the same handle would fail, and there were two memory leaks.

multi stack and that easy handle had already been used to do one or more
easy interface transfers, as then the code threw away the previously used
DNS cache without properly freeing it.

from Curl_client_write

Fixed handling of retransmitted blocks on transmit
Properly aligned data to transmit within packet
Replaced calls to strerror() with Curl_strerror()

thus works reliably on more platforms.

like this in this source file. The quickfix for now is to provide a simple
version for GnuTLS builds. The GnuTLS version of libcurl doesn't yet allow
fully non-blocking connects anyway so this function doesn't get used.

(http://curl.haxx.se/bug/view.cgi?id=1481217), with follow-ups by Michele Bini
and David Byron. libcurl previously wrongly used GetLastError() on windows to
get error details after socket-related function calls, when it really should
use WSAGetLastError() instead.

When changing to this, the former function Curl_ourerrno() is now instead
called Curl_sockerrno() as it is necessary to only use it to get errno from
socket-related functions as otherwise it won't work as intended on Windows.

(http://curl.haxx.se/bug/view.cgi?id=1480821) He found and identified a
problem with how libcurl dealt with GnuTLS and a case where gnutls returned
GNUTLS_E_AGAIN indicating it would block. It would then return an unexpected
return code, making Curl_ssl_send() confuse the upper layer - causing random
28 bytes trash data to get inserted in the transfered stream.

The proper fix was to make the Curl_gtls_send() function return the proper
return codes that the callers would expect. The Curl_ossl_send() function
already did this.

#ifdef around WSAEDISCON in strerror.c.

(more logical).

HAVE_PROCESS_H added for all except scc.

systems

transfers. They are done on non-windows systems and translate CRLF to LF.

the stream (wrongly) lacks a proper zlib header. This seems to be the case on
too many actual server implementations.

can and will use more than one socket

to allow/support character conversions

the control connection when using FTP, for example when you remove an easy
handle from a multi stack.

to my previous brain-damaged version)

one

about what sockets to wait for what action on

CURLOPT_TIMEOUT, the _longer_ time would wrongly be used for the SSL
connection time-out!

code rearrange to fit the future better.