On Tue, Oct 16, 2001 at 12:53:46PM +0400, Alexander V. Lukyanov wrote: > Does attached workaround help it?
Can't test it right now (server's down), I'll let you know when it's back. > > The server *should* return another 2xx or 4xx response for the transfer > > (success or aborted) first; it doesn't. This needs a workaround, but > > For braindamaged servers there is 'set use-abor no', BTW. Well, the more common ones should be worked around whenever possible-- generally by the time you find out you need use-abor (etc), you've already lost a connection. (For ones that aren't reasonable to work around, it should try to detect--on some busy servers, losing a control connection can mean retrying for hours. Not fun. :) > This is strange, because server should close control connection when > it receives QUIT. lftp would notice this. Maybe ABOR did not actually work? > 225 reply means that data connection is still open, according to RFC. Maybe; it would respond to CWD, etc, but it might be doing that and leaving the control connection open. People need to be shot for running warftpd in the first place ... worthless program. > This only matters for receiving OOB messages. Ftp server must not send them, > so it does not matter for client. Hmm, wonder why it was doing that, then. -- Glenn Maynard
