in the urlglobbing just now, fixed in the debian bug tracker as Bug#203827

the file in the dist-hook to make distcheck run fine

make sure it set async false even when using ipv6 (made test case 20 fail
before)

build libcurl to use ares for asynch name resolves.

FTP use the correct directories!

Reported in bug report #783116

  which turned up to be due to the number of dots in the 'domain'. I've now
  made curl follow the the original netscape cookie spec less strict on that
  part.

 with FOLLOWLOCATION and chunked transfer-encoding, as libcurl would not
 properly ignore the body contents of 3XX response that included the
 Location: header.

connects and otherwise enforced tunnel-thru-proxy requests), the same
authentication header is also wrongly sent to the remote host.

The name and password can then be captured by an evil host and possibly get
used for malicious purposes.

style like other faked HTTP headers when NOBODY and HEADER are used.

unsigned and we want this to be able to hold -1 for illegal/unset values.

"double slash" as indicating the root directory. In the RFC1738-fix of April
30, that ability was removed (since it is not the "right" way).

SSL/CA.

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.

CVS. This will be updated by the configure script, and a default is placed
here by the maketgz script.

a separate struct properly.

than the remote server's. That is, both the server and the proxy can in
fact require NTLM auth.

connectdata to work as expected

with a blank argument is a bad idea. Now skip blanks.

credentials.

of the sessionhandle struct, as that was not good.