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).

 return CURLE_OK no matter what happens.

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

I edited somewhat and removed trailing whitespaces.

chunked encoding.

 there seem to be non-compliant FTP servers out there that return 200,
 so we accept any '2xy' response now.

Ralph Mitchell's notification.

slash after the host name, but still a ? and following "parameters".

made the Last-Modified (faked) header look correct using GMT always

miss the first letter

and 12 following hexadecimal letters, which seems to be what IE uses.
This makes curl work smoother with more stupidly written server apps.

Worked this out together with Martijn Broenland.

also subsequently free the ssl struct if the connection struct is to be
deleted

comparisons before re-using SSL connections and re-using SSL connection IDs.

disables the host name check in the FOLLOWLOCATION code. With that option
set, libcurl will send user+password to all hosts.

ConnectionExists() when first doing a proxy connecto to a HTTPS site and then
switching over to a HTTP connection to the same host.

This fix corrects the problem.

change options on an SSL-enabled connection between requests.

"It is a DEMO certificate and was never intended to be in any list of trusted
CA certificates."

(quote by Götz Babin-Ebell, trustcenter.de)

We need to make sure that when we init a 'connectdata' struct and then
afterwards check for and re-use another one, we must be careful so that the
newly set values are transmitted and used in the surviving connectdata struct.