with the accelerated writing of server input and response request files
in test harness sws server.

instead of the stack.

to disk, trying to defeat file and disk write-behind algorithms

and --help options.

result file verifications to allow the test server to completely write
out all files

result file verifications to allow the test server to completely write
out all files

easy. This was reported not working by Penugonda Chenna Reddy in
http://curl.haxx.se/mail/lib-2008-04/0046.html but I fail to repeat that
problem.

discussed in http://curl.haxx.se/mail/lib-2008-04/0291.html

  properly acknowledging the timeout values, like if you pulled the network
  plug in the midst of it.

  return code in the Negotiate code.

  (http://curl.haxx.se/bug/view.cgi?id=1942022) pointing out a mistake in the
  lib/Makefile.vc[68] makefiles' release-ssl-dll target.

  you used -i and -I.

  was not checked for a NULL return, in the Negotiate code.

by Ben Combee where libcurl would send the wrong cookie to a redirected
server.  libcurl was doing the right thing in this test case.

Fix qssl.c wrong error message
Upgrade OS400 wrappers and makefiles to 7.18.1

  Define HAVE_GSSMIT if <gssapi/{gssapi.h,gssapi_generic.h,gssapi_krb5.h}> are
  available, otherwise define HAVE_GSSHEIMDAL if <gssapi.h> is available.

  Only define GSS_C_NT_HOSTBASED_SERVICE to gss_nt_service_name if
  GSS_C_NT_HOSTBASED_SERVICE isn't declared by the gssapi headers. This should
  avoid breakage in case we wrongly recognize Heimdal as MIT again.

assumes proxies to use

  message when libcurl doesn't get a 220 back immediately on connect, I now
  changed it to be more specific on what the problem is. Also worth noticing:
  while the bug report contains an example where the response is:

    421 There are too many connected users, please try again later

  we cannot assume that the error message will always be this readable nor
  that it fits within a particular boundary etc.

  ares_expand_string.c