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.

bug!!

we might need to check for some other tools too that on Solaris are put
in those weird dirs...

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

the distribution archive, as it isn't sure zlib is present everywhere. Those
who care much for compressed help should regenerate the file.

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

possibly crlf newlines.

slash

necessarily the root...

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

that is works... and it did! ;-)

SSL/CA.

set a conditional for the makefile if we know the CA path or not

need it.

lowered the number of retries to 10

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.

CHANGES.2002.