Re: [Proftpd-devel] FTP Protocol ABOR Support

[TJ S. <tj...@ca...>]

wrl>completed in the transferlog/xferlog, even though an ABOR was issued.

This is due to a design decision made a long time ago, I think.  At one
time, proftpd was designed to handle FTP commands asynchronously.  But
this was changed (I don't know why, probably for design simplicity), and
now proftpd processes all FTP commands synchronously.  For the large
majority of cases, this is not a problem, as most FTP clients themselves
are synchronous.

wrl>>From reading RFC959, I believe that ProFTPD should immediately close the
wrl>data connection upon receipt of an ABOR command on the control connection:
wrl>
wrl>  "In the second case, the server aborts the FTP service in
wrl>   progress and closes the data connection, returning a 426
wrl>   reply to indicate that the service request terminated"

For better or worse, RFC959's language is vague enough to leave
implementors wiggling room on such behaviors.

wrl>Does ProFTPD follow the same behavior for RETR+ABOR command sequences?

Yes.

wrl>Thanks, in advance, for any insight.

Is there a particular reason you need to have the full ABOR functionality?

Cheers,
TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Are you not ashamed of your eagerness to possess as much wealth, reputation
   and honors as possible while you do not care for nor give thought to wisdom
   or truth, or the best possible state of your soul?

     -Socrates

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~