test a report that the size didn't work, but these test cases pass.

  particular state for the control connection like it did before for implicit
  FTPS (libcurl assumed such control connections to be encrypted while some
  FTPS servers such as FileZilla assumes such connections to be clear
  mode). Use the CURLOPT_USE_SSL option to set your desired level.

so split a long sprintf into two calls to get below that number.

Fixed!

  researching it, it turned out he got a 550 response back from a SIZE command
  and then I fell over the text in RFC3659 that says:

   The presence of the 550 error response to a SIZE command MUST NOT be taken
   by the client as an indication that the file cannot be transferred in the
   current MODE and TYPE.

  In other words: the change I did on September 30th 2008 and that has been
  included in the last two releases were a regression and a bad idea. We MUST
  NOT take a 550 response from SIZE as a hint that the file doesn't exist.

(to get correct linkage on Windows).

Added _USE_32BIT_TIME_T to avoid runtime warning. Applies to
VC-2008+ only.

RETSIGTYPE and HAVE_PROCESS_H.

Fixed!

  (http://curl.haxx.se/bug/view.cgi?id=2221237) that identified an infinite
  loop during GSS authentication given some specific conditions. With his
  patience and great feedback I managed to narrow down the problem and
  eventually fix it although I can't test any of this myself!

and I edited it to also get duped by ares_dup().

support (e.g. Minix)

  (http://curl.haxx.se/bug/view.cgi?id=2351645) that identified a problem with
  the multi interface that occured if you removed an easy handle while in
  progress and the handle was used in a HTTP pipeline.

  bad fclose() after a fatal error had occured.
  (http://curl.haxx.se/bug/view.cgi?id=2382219)

Also discussed on the ml.

OpenWatcom C, and condoned by SUS)

latest releases to remain ABI compatible.

OpenWatcom C)

buffer to shrink instead of expand if a reply contained 8 or more records.