| Age | Commit message (Collapse) | Author |
|---|
|
also affecting NTLM and Negotiate.) It turned out that if the server responded
with 100 Continue before the initial 401 response, libcurl didn't take care of
the response properly. Test case 245 and 246 added to verify this.
|
|
But this works just fine on my host. Plain HTTP POST using Digest.
|
|
|
|
|
|
the failed connect "immediately".
|
|
|
|
|
|
|
|
|
|
|
|
send any data anyway. Probably the bug Tom Moers noticed.
|
|
|
|
|
|
AUTH has been received successfully.
|
|
up in several chunks when read.
|
|
functions. This enabled me to add a function that automatically delays between
each byte, to proper test curl's ability to read FTP server responses sent in
many (small) chunks. See also upcoming libcurl fixes...
|
|
function was fixed to use the proper proxy authentication when multiple ones
were added as accepted. test 239 and test 243 were added to repeat the
problems and verify the fixes.
|
|
|
|
test 154
|
|
|
|
|
|
option instead of just assuming it is present.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
more involved, but should hopefully not generate any compiler warnings on
win32 systems (that can't check the socket based on the numeric).
|
|
is no longer only present when built with SSL support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
style build
|
|
|
|
on a host with a buggy resolver that strips all but the bottom 8 bits of
each octet. The resolved address in this case (192.0.2.127) is guaranteed
never to belong to a real host (see RFC3330).
|
|
|
|
|
|
|
|
|
|
the default options set in the Makefile
|
|
between platforms
|
|
these days...!
|
