Dreamweaver Remote Server file transfer cancellation and timeout handling

What happens when you cancel a multi‑file sync?

The user‑initiated Cancel sends an abort request to the active transfer thread. For FTP this is the ABOR command, for SFTP it closes the SSH channel, and for FTPS it sends a TLS‑level abort. The abort stops the transfer of the current file mid‑stream, but Dreamweaver does not automatically delete or roll back the partially written file on either the local or remote side. Consequently, partial artifacts remain and must be cleaned up manually.

How does the exposed connection timeout interact with internal retry/resume logic?

The timeout you set in the Site Definition only governs the TCP socket connect timeout for the control channel. It does not affect data‑channel idle timeouts, per‑file retry limits, or resume behavior.

• FTP: After a control‑channel timeout the internal retry mechanism attempts a limited number of reconnects (typically 2‑3) before aborting the job. The REST command is not used, so resume is not attempted.
• SFTP: The underlying library may support a restart at the last successfully written byte if the server advertises the POSIX‑rename extension, but Dreamweaver does not expose a resume option. Therefore, even when a restart is possible, the partial file is left on disk and must be removed manually.
• FTPS: Inherits FTP’s abort semantics; some FTPS servers may ignore the ABOR command over TLS, which can leave the transfer hanging until the server‑side idle timeout expires.

Is manual cleanup required after a timeout or cancellation?

Yes. After a user Cancel or a timeout‑induced abort, the session is closed and subsequent transfers require a new login. Dreamweaver does not perform automatic cleanup of temporary or partially transferred files, so you should inspect both local and remote directories for incomplete files and delete or re‑transfer them as needed.

Verification steps (optional)

1. Define a remote site (FTP, SFTP, or FTPS) in Dreamweaver.
2. Start a large multi‑file Get/Put or site synchronization.
3. Click Cancel after a few files have transferred.
4. Check the local and remote folders for files that are smaller than expected or have a temporary extension.
5. Repeat the test with a very low connection timeout (e.g., 1 second) and disconnect the network to force a control‑channel timeout; observe whether the job ends with an error and whether partial files remain.
6. Open Window → Results → Logging to confirm ABOR (FTP), channel‑close (SFTP), or TLS abort (FTPS) messages.