Renamed the curl_ftpssl enum to curl_usessl and its enumerated constants,
creating macros for backward compatibility.

generic, and more consistent with each other.

case 615 to test an SFTP upload failure.

and allow reuse by multiple protocols. Several unused error codes were
removed.  In all cases, macros were added to preserve source (and binary)
compatibility with the old names.  These macros are subject to removal at
a future date, but probably not before 2009.  An application can be
tested to see if it is using any obsolete code by compiling it with the
CURL_NO_OLDIES macro defined.

Documented some newer error codes in libcurl-error(3)

renamed LDAP(S) messages from 'yes' to 'enabled'.

cleaning up after an OOM condition in curl_multi_add_handle

low-level ftp_readresp() function. Hopefully adressing bug #1779054.

by Kris/tinker105 in bug #1779054) and mention the torture tests.

Adding DOCS file in OS400 installation library with license and various other documentation text files.
Setting character set of OS400 installed source components

out that libcurl didn't deal with large responses from server commands, when
the single response was consisting of multiple lines but of a total size of
16KB or more. Dan Fandrich improved the ftp test script and provided test
case 1006 to repeat the problem, and I fixed the code to make sure this new
test case runs fine.

multiple lines (similar to test case 1003).

characters.

empty proxy server is selected.

just because if I do that automake does funny things automatically with the
makefile.sh file in that directory and thus doing it this way was a quick
work-around that annoyance!

default now to verify cert unless data->set.ssl.verifypeer is 0.

out that doing first a file:// upload and then an FTP upload crashed libcurl
or at best caused furious valgrind complaints. Fixed now by making sure we
free and clear the file-specific struct properly when done with it.

out that libcurl didn't deal with very long (>16K) FTP server response lines
properly. Starting now, libcurl will chop them off (thus the client app will
not get the full line) but survive and deal with them fine otherwise. Test
case 1003 was added to verify this.

future

that verfies ridiculously long server response lines. Also changed sprintf
to snprintf in a few places.