Version : curl-7.9.8-5 on red hat linux 9 / i386
command line used : curl -g -O $URL
URLs tested that behave wrongly :
ftp://uel003r2a:333qwe@rcum.uni-mb.si/WWW//david.sig
( FTP command CWD with no parameter not handled )
ftp://uel003r2a:333qwe@rcum.uni-mb.si/%5buel003r2a%
5d/%5b.WWW%5d/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[uel003r2a]/WWW/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000]/uel003r2a/WWW/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/[-
]/uel003r2a/stuff/[-]/www/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/[-
]/uel003r2a/stuff/[-]/[.www]/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000
]/uel003r2a/STUFF/../WWW/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000
]/uel003r2a/STUFF/[-.WWW]/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000
]/uel003r2a/STUFF/[-.WWW]NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000
]/uel003r2a/STUFF/[uel003r2a.WWW]/NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a
[000000
]/uel003r2a/STUFF/[uel003r2a.WWW]NDA.PNG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/
[UEL008R2A]/WWW/JAZ.JPG
ftp://uel003r2a:333qwe@rcum.uni-mb.si/UMB1%3a%
3aSYS$SPECIFIC%3a[FAL$SERVER
]NETSERVER.LOG;type=a
(downloaded file has CR+LF instead of LF ;
manual /bin/ftp downloads
OK)
ftp://uel003r2a:333qwe@rcum.uni-mb.si/UMB1%3a%
3a/SYS$SPECIFIC%3a/[FAL$SERVER
]/NETSERVER.LOG
ftp://uel003r2a:333qwe@rcum.uni-
mb.si/test/testfile_upasc.txt
(downloaded file has all content in one line , no CR or
LF)
ftp://uel003r2a:333qwe@rcum.uni-
mb.si/test/testfile_upasc.txt;type=a
(downloaded file is wrong ( has CR+LF instead of LF
only ))
ftp://uel003r2a:333qwe@rcum.uni-
mb.si/test/TESTFILE_UPASC.X4R3;type=a
(downloaded file is wrong ( has CR+LF instead of LF
only ))
ftp://stein:test12@naomi/te1//test.txt
( again FTP command CWD with no parameter not
handled )
ftp://stein:test12@naomi/te1/%2ftmp/tmp1.txt
(wrong handling of CWD /tmp)
The complete table of tests I have done is at
http://rcum.uni-mb.si/~uel003r2a/ftp_url_test.html
it includes some HTML comments, so look at its source.
This is discussed on the curl-
users@lists.sourceforge.net mail list under the subject
of "FTP URL bugs", see first message at
http://curl.haxx.se/mail/archive-2003-04/0206.html
Logged In: YES
user_id=1110
On the ASCII download problems, is it just the CRLF
problems? I realize that libcurl should convert CRLF to
plain LF on downloads on a unix machine, while on Windows it
should remain CRLF. Likewise, uploading ASCII on FTP should
on unix make LF become CRLF while a windows machine already
uses CRLF (typicly).
Or am I oversimplifying?
Logged In: YES
user_id=1110
Hello?
Logged In: YES
user_id=291427
About the ASCII conversions, the FTP RFC ( RFC959 ) surely
describes the procedure in detail.
I believe the client must convert the data in some standard ftp
format and then the server converts it to its own format.
As I said in my private mail, I really don't have any free time
for curl hacking.
Logged In: YES
user_id=1110
To me, the explanations in RFC959 and the TELNET RFC854 are
not at all that clear that you seem to think they are.
Anyway, I'm making this an item in the TODO as no one seems
to be willing to fix this or help out.
Thanks for reporting, closing this report now marked
"later". To be fixed when someone feels this is a concern.