| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
it work again
|
|
|
|
|
|
|
|
|
|
|
|
|
|
connection to avoid re-use of it, since we cannot know in what state it is.
|
|
in the 229-reply servers respond on a EPSV command and bail out better if
the reply string is not valid RFC2428-compliant.
|
|
|
|
isn't. In fact, it might be, but we have no idea.
|
|
|
|
|
|
|
|
|
|
|
|
after a failed transfer.
|
|
|
|
|
|
|
|
function
|
|
|
|
|
|
|
|
|
|
build libcurl to use ares for asynch name resolves.
|
|
FTP use the correct directories!
Reported in bug report #783116
|
|
style like other faked HTTP headers when NOBODY and HEADER are used.
|
|
unsigned and we want this to be able to hold -1 for illegal/unset values.
|
|
"double slash" as indicating the root directory. In the RFC1738-fix of April
30, that ability was removed (since it is not the "right" way).
|
|
|
|
with a blank argument is a bad idea. Now skip blanks.
|
|
of the sessionhandle struct, as that was not good.
|
|
|
|
contents. Test cases 144 and 145 were added to verify the fix.
Now we deal with return code 450 properly and other codes also do proper
cleanup.
|
|
for FTP command responses take >1 second.
|
|
it is.
|
|
the new socket to non-blocking
|
|
|
|
as otherwise we'll go nuts
|
|
RFC1738, which means it'll use one CWD for each pathpart.
|
|
there seem to be non-compliant FTP servers out there that return 200,
so we accept any '2xy' response now.
|
|
made the Last-Modified (faked) header look correct using GMT always
|
|
|
|
Fix by Richard Gorton.
|
|
when SIZE is used on the file while being in BINARY mode. To work
around that (stupid) behavior, we attempt to parse the RETR response
even if the SIZE returned size zero.
Debugging help from Salvatore Sorrentino on February 26, 2003.
|
|
|
