compiler warning fix since it was Ok and actually
avoids the targeted compiler warning.

Assigning the const value zero to a pointer to function
results in a null pointer value assignment to the function
pointer.

Assignment of any nonzero value is what should result in a
implementation compiler dependent result.

Since what we want to do here is the first case, this should
not trigger compiler warnings related with conversions from
'pointer to data' to 'pointer to function'.

Our autobuild test suite will judge.

and send(). Added needed HAVE_x defines.

to avoid picky compiler warnings, since this is what we want!

on Win32.

- Take in account RLIM_INFINITY.
- Verify that soft limit is actually changed when doing so.
- Show errno in case getrlimit or setrlimit fails.
- Keep file descriptors open only while runing this test.

buffer used to store headers in the SessionHandle failed.

case when 401 or 407 are returned, *IF* no auth credentials have been given.
The CURLOPT_FAILONERROR option is not possible to make fool-proof for 401
and 407 cases when auth credentials is given, but we've now covered this
somewhat more.

You might get some amounts of headers transferred before this situation is
detected, like for when a "100-continue" is received as a response to a
POST/PUT and a 401 or 407 is received immediately afterwards.

Added test 281 to verify this change.

Removed trailing whitespace.

Improve cleanup in case of initialization failure.

test hanging and actually is an indication that there's a condition that is
not being properly handled at some point in the library.

Remove a pair of braces and adjust indentation appropriately.

applies for asynch name resolves in general and not only ares

re-use connections (for pipelining) before the name resolving is done.

as well

'packages/EPM/curl.list.in seems to ignore the --datarootdir setting'