cURL / Mailing Lists / curl-users / Single Mail

curl-users

Re: FTP URL bugs

From: David Balazic <david.balazic_at_uni-mb.si>
Date: Tue, 29 Apr 2003 11:44:49 +0200

Daniel Stenberg wrote:
>
> On Mon, 28 Apr 2003, David Balazic wrote:

[snip]
 
> > ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a[uel003r2a]/WWW/NDA.PNG
>
> I don't want to be a party-killer, but the [ and ] letters are mentioned in
> the RFC1738 to be "unsafe" and as such they should be %-encoded. (Section
> 2.2, page 3.)

Does not help ( I also encoded the "$" ):

[stein_at_juice curl]$ curl -v -O
'ftp://uel003r2a:444qwe@rcum.uni-mb.si/%24el_a%3a%5buel003r2a%5d/WWW/NDA.PNG'
* About to connect() to rcum.uni-mb.si:21
* Connected to rcum.uni-mb.si (164.8.2.10) port 21
> USER uel003r2a
> PASS 444qwe
* We have successfully logged in
> PWD
* Entry path is '$EL_A:[UEL003R2A]'
> CWD $el_a:[uel003r2a]/WWW
curl: (9) Couldn't cd to $el_a:[uel003r2a]/WWW
* Closing connection #0

>
> > ftp://uel003r2a:333qwe@rcum.uni-mb.si/$el_a%3a[000000]/uel003r2a/STUFF/[uel003r2a.WWW]/NDA.PNG
>
> Again, it would be interesting to see in what way these ones failed.

[stein_at_juice curl]$ curl -v -O
'ftp://uel003r2a:444qwe@rcum.uni-mb.si/$el_a%3a[000000]/uel003r2a/STUFF/[uel003r2a.WWW]/NDA.PNG'
* About to connect() to rcum.uni-mb.si:21
* Connected to rcum.uni-mb.si (164.8.2.10) port 21
> USER uel003r2a
> PASS 444qwe
* We have successfully logged in
> PWD
* Entry path is '$EL_A:[UEL003R2A]'
> CWD $el_a:[000000]/uel003r2a/STUFF/[uel003r2a.WWW]
curl: (9) Couldn't cd to $el_a:[000000]/uel003r2a/STUFF/[uel003r2a.WWW]
* Closing connection #0

it fails because it tries to use a single CWD which is not possible with
this
path , unless you do some serious processing. This is like trying to do
the
following ( on a unix system ) with a single CWD :

CWD ../y
CWD /tmp
CWD ../bin

> > 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)
>
> I don't see how downloading is a RFC1738 issue though. It only defines
> URLs... But of course, curl doesn't properly deal with ftp ASCII transfers,
> I've noticed before and I believe there's some issue about this mentioned in
> the TODO.

The TODO of version curl-7.9.8-5 mentions problems with FTP ASCII
upload,
but not download.
 
[snip]

> > ftp://stein:test12@naomi/te1/%2ftmp/tmp1.txt
> > (wrong handling of CWD /tmp)
>
> I think this is another artifact of the same functionality.

[stein_at_juice curl]$ curl -v -O
'ftp://stein:test12@naomi/te1/%2ftmp/tmp1.txt'
* About to connect() to naomi:21
* Connected to naomi.xxx.xx (10.49.xx.xx) port 21
> USER stein
> PASS test12
* We have successfully logged in
> PWD
* Entry path is '/home/stein'
> CWD te1//tmp
curl: (9) Couldn't cd to te1//tmp
* Closing connection #0

 
> > If not instructed otherwise, I will report this bug(s) to the sf.net
> > bugtracker system.
>
> I think that could be good, so that we don't forget it. I don't think we will
> (at least I won't) even try to fix all of them within the nearest time period
> though.
>
> Any possibility you can make the report more detailed then?

Tell me if you need anything else.

-- 
David Balazic
--------------
"Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore
Logan
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-04-29