as otherwise we'll go nuts

  o Save domains in jars like Mozilla does. It means all domains set in
    Set-Cookie: headers are dot-prefixed.
  o Save and use the 'tailmatch' field in the Mozilla/Netscape cookie jars (the
    second column).
  o Reject cookies using illegal domains in the Set-Cookie: line. Concerns
    both domains with too few dots or domains that are outside the currently
    operating server host's domain.
  o Set the path part by default to the one used in the request, if none was
    set in the Set-Cookie line.

RFC1738, which means it'll use one CWD for each pathpart.

 when using the multi interface (too).

content-length made me add test case 60, that does exactly this, but it
seems to run fine...

 return CURLE_OK no matter what happens.

than long and libcurl expects a long...

are set before all system headers, as otherwise we get compiler warnings
on my Solaris at least.

similar is set properly by us first

it had problems withe CA cert and thus we offer a huge blurb of verbose
help to explain to the poor user why this happens.

also now attempt to detect and return the specific CACERT error code.