responded with a single status line and no headers nor body. Starting now, a
HTTP response on a persistent connection (i.e not set to be closed after the
response has been taken care of) must have Content-Length or chunked
encoding set, or libcurl will simply assume that there is no body.

To my horror I learned that we had no less than 57(!) test cases that did bad
HTTP responses like this, and even the test http server (sws) responded badly
when queried by the test system if it is the test system. So although the
actual fix for the problem was tiny, going through all the newly failing test
cases got really painful and boring.

-Log errno in message if setsockopt() fails.

-Close listener socket on major errors.

Place parenthesis surrounding macro parameters so that the use of sread and swrite is more intuitive.

ordinary test suite. Also removed the perror() calls and instead made the
logging output the errno code to ease error tracking using logs.

code. It should however not be the cause of any troubles. He also fixed a
few similar problems in the HTTP test server code.

CURL_SWS_FORK_ENABLED defined it forks for each new connection and thus can
support any amount of connection clients (used for hiper tests and not for the
standard plain curl test suite)

of the end of a chunked-encoded POST request.

"http://somehost?data" as it added a slash too much in the request ("GET
/?data/"...). Added test case 260 to verify.

Added resolve.c to simply resolve a given host name

and sockfilt.c. For good-to-have functions for the servers written in C.

test 154

with binary data.