Transfering filenames w/ spaces

[anonymous]

I am trying to transfer files from a windows 2k pro
platform to a unix system running proftp v1.2.1. The
files that I am transfering contain spaces. The
application does not seem to recognize this and does
not quote or escape the spaces when the remote host
(unix) assumes that a space is a inter-file seperator.

Ie. the file "this is a test" would look to unix as
four files "this" "is" "a" "test". as a space is
considered part of the IFS. To get around this the
client needs to do some custome parsing if it finds
the remote site is a unix host. (ie, escaping the
spaces, or converting them (user definable?)).

[codesquid]

Can you please enter the command "SYST" (without quotes) to
the server and send me the reply?

[anonymous]

Logged In: NO

I am not on my own computer right now but here is the SYST
info from the server:

---

C:\>ftp ftp.chaven.com
Connected to ftp0.chaven.com.
220 ProFTPD 1.2.2 Server (ProFTPD Default Installation)
[ftp0.chaven.com]
User (ftp0.chaven.com:(none)): xxxxxx
331 Password required for xxxxxx.
Password:
230 User ftpadmin logged in.
ftp> quote syst
215 UNIX Type: L8
ftp>

---

[anonymous]

Logged In: NO

I am also having similar problems with filenames with
spaces.

Filenames with spaces are successfully uploaded, but the
File Attributes fails.

[That is, the STOR command is sent without quoting, and
succeeds. The SITE CHMOD command, however, gets a 500
response (not understood)]

I am not sure of the brand name of the FTP server (it
doesn't say on connect) but SYST gets a "215 Unix Type: L8"
response.

I am not sure if this is considered a new bug, or part of
the same one.

[anonymous]

Logged In: NO

i think the client would need to send the file as "this\ is\
a\ test", assuming the functionality of the syntax is that
of the command line. if that's what you meant by escaping
the spaces then sorry to waste your time

[eddan]

Just did a test on a ftp server that responded UNIX Type: L8
and everything seemed to work.

Since this is an extremely old item, I'll assume this is
fixed and will close it. If you still experience this bug,
please re-open it.