need it.

accidentally re-use the connect_addr field, as that might no longer be
around. Fix verified by Tracy Boehrer who basicly debugged and tracked down
this problem.

connectdata to work as expected

credentials.

of the sessionhandle struct, as that was not good.

   CURLOPT_SSL_CTX_FUNCTION to set a callback that gets called with the
   OpenSSL's ssl_ctx pointer passed in and allow a callback to act on it. If
   anything but CURLE_OK is returned, that will also be returned by libcurl
   all the way back. If this function changes the CURLOPT_URL, libcurl will
   detect this and instead go use the new URL.

   CURLOPT_SSL_CTX_DATA is a pointer you set to get passed to the callback set
   with CURLOPT_SSL_CTX_FUNCTION.

a "plain" Negotiate as well.

but the infrastructure is there.

to add more method in the future.

added.

SOCKS5 fix as suggested by Jis in bugreport #741841.

 set to "".  This frees the application from having to know which encodings
 the library supports.

Ralph Mitchell's notification.

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

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.

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.

Fix by Richard Gorton.

than 5 could cause a segfault.

way for emacs, and vim users should provide a similar non-polluting style

only allocating the scratch memory buffer once it is needed and not always
in the handle.

was due to a missing fix for the password prompting

"username" will cause libcurl to prompt for password. Bryan Kemp noticed.

test case 136 is added for this