Kenneth Loafman added the comment:
It's been a couple of years since I reported this and its entirely
possible that the updated ProFTPd I'm now testing against has been
fixed, and that ftplib has evolved since then. Short of one of you
testing the current ftplib against a current
Kenneth Loafman added the comment:
Clearly not valid if you are strictly RFC compliant, however, if you
want to be functional in the real world then it needs to be addressed.
ProFTPd is not the only server that handles things this way, so from a
functionality and compatibility standpoint, it
Kenneth Loafman added the comment:
Yes, there is no 1xx response. I've attached a log between ncftp client
and ProFTPd 1.3.1-6ubuntu1 that clearly shows no 1xx after the 226.
--
Added file: http://bugs.python.org/file13634/trace
___
Python tr
