subjectAltNames when matching certs. This is apparently detailed in RFC2818
  as the right thing to do. I had to add configure checks for inet_pton() and
  our own (strictly speaking, code from BIND written by Paul Vixie) provided
  code for the function for platforms that miss it.

Jeremy Friesner.

sends off the previously set cookie. This also concerns CURLOPT_REFERER.
This fix should stop this.

after a failed transfer.

my_getaddrinfo() has been called (and wait has been set to TRUE), we check
if the name already is resolved and if so don't return wait status to the
parent. This can happen with IP-only names.

properly or risk getting into trouble!

cleanups.

reset the authentication state to make it restart on the next connection.

This of course because NTLM is connection-oriented, whilst all other
authentication schemes are not.

is over or not, as if it isn't we shall not begin any PUT or POST operation.

This cures bug report #805853, and test case 88 verifies it!

NOT free the existing hash entry when we try to add a new one that matches
an existing entry. We now instead free the new one, and make the parent
function use the old entry's struct instead.

"Negotiate" authentication as well.

not used by any code in libcurl!

Problem tracked down by Bjorn Reese.

more in the same style as other curl source code. The only actual code change
is an added check after a malloc() call.

properly if no auth is available

CURLINFO_HTTPAUTH_AVAIL and CURLINFO_PROXYAUTH_AVAIL

2. made Curl_http_auth_act() reset 'authavail' unconditionally

authentication negotiations needed for NTLM, Digest etc.