as a problem serious enough to skip the final QUIT command before closing
the control connection. To avoid the risk that it will "hang" waiting for
the QUIT response. Added test case 161 to verify this.

we won't try to QUIT the control connection and risk "hanging" waiting for
a response. Test case 161 verifies this. The quit-sending function was
also made static.

we tell valgrind to use that to send the logfile to

less

160 shows.

We got no data and we attempted to re-use a connection. This might happen if
the connection was left alive when we were done using it before, but that was
closed when we wanted to read from it again. Bad luck. Retry the same request
on a fresh connect!

Deleted the sockerror variable again, it serves no purpose anymore.

to re-use a connection that is closed when re-used and libcurl should then
make a new fresh connection and use instead

length limit of the hostname part of the URL.

most 1.1 connections will be closed. The case where it gets closed anyway
is subject for a new separate test.

it actually will close. This is after all what HTTP 1.1 says a server should
do.

attached. And some cosmetic fixes.

the execution of the tests

added various logging info

display all logs and only logs with relevant data when a test fails and -p
is used.

should be used

now cause the resolve function to return NULL immediately

some bad thinking on my part.