Rebex incorrectly recognizes NOOP 200 server response as premature transfer success

0 votes
asked Dec 7, 2016 by MerliN (260 points)


I'm using NOOP command during transfers (KeepAliveDuringTransfer option) to avoid control connection being closed by routers/modems of our users leading to a timeouted transfer.

However, one of the servers responds with "200 I successfully done nothin'." and Rebex considers it a successfull transfer marker and throws an FtpException with a "Premature success response was received from the server even though the upload is still in progress" message.

Please add handling for this specific message (ignore it) :)

Thank you.

Applies to: Rebex FTP/SSL

1 Answer

0 votes
answered Dec 7, 2016 by Lukas Pokorny (128,250 points)
edited Dec 20, 2016 by Lukas Pokorny

Thanks for letting us know, detecting NOOP responses is quite tricky. We added this message to the ignore list.

This has been released with Rebex FTP/SSL 2016 R3.