I received the following from an associate who posted a question here:
"The user should fix his software. The RFC 640 explicitly specifies that
(I use | here to separate fields):
a. Single-line responces are in the format:
|Three-digit response code| |Human-readable message|newline|
b. Multi-line responces are in the format:
|Three-digit response code|-|Human-readable message|newline|
optional continuation lines
|Three-digit response code| |the last continuation line|newline|
A client program should be prepared to deal with either format."
However the following simple test on DU shows it doesn't conform to the
RFC as the last continuation line does not contain a response code.
Is there a recommended ftp or fix for DU?
The "user" in this case is IBM's ftp on MVS/ESA (or some such) and
"asking the user to fix his code" is not a practical option.
(the target machine is running DU 4.0B)
200 PORT command successful.
150 Opening ASCII mode data connection for x.lis (198.80.11.41,4065).
230-WARNING! 3 bare linefeeds received in ASCII mode
File may not have transferred correctly.
226 Transfer complete.
local: SYS$SYSROOT:[SYSMGR]X.LIS;23 remote: x.lis
5 bytes sent in 00:00:00.00 seconds (4.88 Kbytes/s)
Received on Sat Jul 18 1998 - 07:42:39 NZST