Bugs item #770755, was opened at 2003-07-14 02:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=770755&group_id=976

Category: ftp
Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Submitted By: David Gardner (pastie)
Assigned to: Daniel Stenberg (bagder)
Summary: CWD with null argument fails on most ftp servers

Initial Comment:
Line 1982 in file lib/ftp.c reads:
      /* RFC 1738 says empty components should be
respected too */

However, upon issuing a CWD with a null argument, all
ftp servers I tested (several large sites, including
reply with an error 501 :
501 Invalid number of arguments.

Hence any ftp URLs with an empty component (ie, two
slashes after one another at some point after the
hostname) cause the ftp CWD to fail. eg.
ftp://host.example.com//path/file

Additionally, this RFC1738 requirement conflicts with
the ftp specification in RFC959, which states that the
CWD command _must_ have an argument.

Possibly it is necessary to detect this case of
CWD+null being unsupported and skip the error and stop
any future sending of CWD+null over that connection?

[problem shown up by use of camE with libcurl, but
occurs for all urls constructed as such]

curl -V:
curl 7.10.5 (i386-pc-linux-gnu) libcurl/7.10.5
OpenSSL/0.9.7b ipv6 zlib/1.1.4

Name+email: David Gardner <curl-bugs [at] icmfp [dot] com>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=770755&group_id=976

-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
Received on 2003-07-14