- Mar 31, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Mar 30, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Mar 29, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
send any data anyway. Probably the bug Tom Moers noticed.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
AUTH has been received successfully.
-
Daniel Stenberg authored
up in several chunks when read.
-
Daniel Stenberg authored
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...
-
- Mar 28, 2005
-
-
Daniel Stenberg authored
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.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
test 154
-
- Mar 22, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
When cross-compiling, we do some better checking for the NI_WITHSCOPEID option instead of just assuming it is present.
-
Gisle Vanem authored
-
Gisle Vanem authored
-
Daniel Stenberg authored
-
Dan Fandrich authored
-
- Mar 21, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
more involved, but should hopefully not generate any compiler warnings on win32 systems (that can't check the socket based on the numeric).
-
Daniel Stenberg authored
is no longer only present when built with SSL support.
-
Daniel Stenberg authored
-
- Mar 20, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Mar 19, 2005
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Mar 18, 2005
-
-
Dan Fandrich authored
-
Dan Fandrich authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
style build
-
Daniel Stenberg authored
-
- Mar 17, 2005
-
-
Dan Fandrich authored
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).
-
Dan Fandrich authored
-
Daniel Stenberg authored
-