when logging in), the operation will fail since libcurl does detect this and
  thus fails to issue the correct command:
  http://curl.haxx.se/bug/view.cgi?id=1693337

recently

one over to KNOWN_BUGS

plus made --pass work on an SSH private key as well.

Dependencies are now put in external file depend.dj.

  1) the progress callback gets called more frequently (at times)
  2) libcurl *might* call the callback when it receives a signal

test, fixing KNOWN_BUGS #11.  Fixed some tests to more accurately specify
their required servers and features.

specific SSL library that might be used, and I cut out the closepolicy stuff
that we no longer support

  -v, --trace and --trace-ascii, since it could really confuse the user.
  Clarified this fact in the man page.

there is an environment variable set)

New FTP CCC functionality - adds passive and active mode to accomodate for different server behaviour

New FTP CCC functionality - adds passive and active mode to accomodate for different server behaviour

AC_PATH_PROG was not used properly.

  5).

  the multi interface and connection re-use that could make a
  curl_multi_remove_handle() ruin a pointer in another handle.

  The second problem was less of an actual problem but more of minor quirk:
  the re-using of connections wasn't properly checking if the connection was
  marked for closure.

SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/

  to the debug callback.

- Shmulik Regev added CURLOPT_HTTP_CONTENT_DECODING and
  CURLOPT_HTTP_TRANSFER_DECODING that if set to zero will disable libcurl's
  internal decoding of content or transfer encoded content. This may be
  preferable in cases where you use libcurl for proxy purposes or similar. The
  command line tool got a --raw option to disable both at once.

instead focus on explaining on how the libs differ from each other

  and CURLOPT_CONNECTTIMEOUT_MS that, as their names should hint, do the
  timeouts with millisecond resolution instead. The only restriction to that
  is the alarm() (sometimes) used to abort name resolves as that uses full
  seconds. I fixed the FTP response timeout part of the patch.

  Internally we now count and keep the timeouts in milliseconds but it also
  means we multiply set timeouts with 1000. The effect of this is that no
  timeout can be set to more than 2^31 milliseconds (on 32 bit systems), which
  equals 24.86 days.  We probably couldn't before either since the code did
  *1000 on the timeout values on several places already.

  platforms.