Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stan!imp From: imp@Solbourne.COM (Warner Losh) Newsgroups: comp.protocols.tcp-ip Subject: Re: Problem with WIN/TCP's secure FTP Message-ID: <1991Feb11.182119.3253@Solbourne.COM> Date: 11 Feb 91 18:21:19 GMT References: <09F0D6D7E020051A@crl.aecl.ca> Organization: Solbourne Computer, Inc., Longmont, CO Lines: 44 In article <09F0D6D7E020051A@crl.aecl.ca> TANNERC@CRL.AECL.CA (CHRISTOPHER TANNER) writes: >I am FTP'ing from VMS to another machine, the 'ls' command is actually sent >as 'ls' (ls followed by 2 blanks). Are you sure? I'm about 99% positive that it sends out an NLST command when you type 'ls' to the prompt and a LIST command when you type 'dir'. I wouldn't doubt that it is putting an extra space at the end, however. >Who is in error here. Is Wollongong violating the standard, or SGI and NOS/VE >being too fussy? SGI and NOS/VE appear to be not conforming to the standard. To quote RFC 959, page 46: "The command codes and the argument fields are separated by ONE OR MORE spaces." (emphasis mine) So, the path name doesn't begin until after the second space[*]. Since there should be a pair after the second space, this makes the pathname argument NULL, so the implementation should list the current directory. This is due to the following in the description of LIST(pp 32, ibid): "If the pathname specifies a directory [...] If the pathname specifies a file [...]. A null argument implies the user's current working or default directory." and in NLST (p 33 ibid): "A null argument implies the current directory" If it was me, I'd file this as an MR to TWG, none the less, since it is causing interoperability problems. Warner -- [*] I guess a case could be made here that if there are to be no arguments, then the command should be immediately followed by a . However, other places call this argument a NULL argument, rather than a missing argument. -- Warner Losh imp@Solbourne.COM We sing about Beauty and we sing about Truth at $10,000 a show.