Skip to content

Automatic Reconnection

Robin Rodricks edited this page Jan 16, 2023 · 14 revisions

Settings

  • Config.SslSessionLength - Number of FTP responses after which we automatically reconnect to the FTP server. Only honored for SSL connections, and ignored for plaintext FTP connections. Set it to 0 to disable automatic reconnection. Default: 750.

How does automatic reconnection work?

At various intervals, we need to reconnect to the FTP server automatically.

  • The FTP server has disconnected us in-between a file transfer, so we need to reconnect and resume the file transfer.
  • We predict that the FTPS connection will get corrupted due to OS bugs, so to prevent this, we preemptively disconnect and reconnect on our own.

FTP Server disconnects midway

This happens during upload and download, and is handled within UploadFileInternal (sync/async) and DownloadFileInternal (sync/async).

These functions detect if the FTP connection was lost and automatically try to reconnect and resume the transfer.

It is always enabled and does not require configuration as such.

FTP Connection gets corrupted

This is only needed and enabled for FTPS/SSL connections and not for plaintext FTP.

We noticed that the underlying .NET SSL stream gets "corrupted" (goes into a unrecoverable state and throws an IOException) after around 900 FTP responses are received from the server. So we developed this system to bypass this limitation: we count the FTP responses received, and then pre-emptively disconnect and reconnect to the FTP server. Please note that this is a bug in the .NET runtime and not with FluentFTP.

It is enabled by default but can be disabled. You can configure it using the setting Config.SslSessionLength (docs above).

reconnect diagram

Clone this wiki locally