outside its given buffer. Discovered and reported by James Bursa.

by Gisle Vanem

a range of a document beyond its size, caused libcurl to "hang" until the
server closed the connection and then it returned error 18.

This is bad. This way, we don't return any error at all, which isn't nice
either, as we need to alert the app somehow that the request range was out
of size.

and gcc, to set the -mimpure-text link flag for linking the lib better.

what particular ares version that is being used.

run out of memory.

my upcoming automated test gets crazy if not

curl and libcurl. -t is not used anywhere automated yet, and it does already
identify memory leaks on failed allocations. Work to do.

--capath. Using -k together with one of those just means that the result
of the CA cert check is ignored (but displayed if -v is used).

done even if the result is ignored, as some sites seem to require that.

we might not get a body when we get a 401 with a set of WWW-Authenticate:
headers. This fixes the problem Kevin Roth detected in 7.10.8-pre4 and pre5.
Verified by test case 91.