assumes proxies to use

  message when libcurl doesn't get a 220 back immediately on connect, I now
  changed it to be more specific on what the problem is. Also worth noticing:
  while the bug report contains an example where the response is:

    421 There are too many connected users, please try again later

  we cannot assume that the error message will always be this readable nor
  that it fits within a particular boundary etc.

  ares_expand_string.c

  GET simply because previously when you set CURLOPT_NOBODY to TRUE first and
  then FALSE you'd end up in a broken state where a HTTP request would do a
  HEAD by still act a lot like for a GET and hang waiting for the content etc.

example programs.

removed

133 - Setting CURLOPT_NOBODY to "false" causes cURL to wait for content if a
      content-length header is read
added

done

$capath is known to configure, so it can be defined in config.h instead.

  application to provide data for a multipart with the read callback. Note
  that the size needs to be provided with CURLFORM_CONTENTSLENGTH when the
  stream option is used. This feature is verified by the new test case
  554. This feature was sponsored by Xponaut.

normal build/install (only with the 'make check' target), so that a
build failure in the examples isn't fatal.

since they're still not clear enough to be to sort about before 7.18.1

  path didn't work properly but now it does!

  the progress callback for the first (potentially huge) piece of body data
  sent together with the POST request headers in the initial send().

  libcurl wasn't built to use OpenSSL as that is a prerequisite for this
  option to function!

functional if libcurl is built against OpenSSL

  case 617 (which was added by Daniel Fandrich 5 Mar 2008).