Differences

This shows you the differences between the selected revisions of the page.

resume 2022-05-31 resume 2026-06-03 (current)
Line 14: Line 14:
Reasons not to do that: Reasons not to do that:
  * As the file is uploaded to a temporary name, it is technically a new file, even though the file with target name already exists. As such:   * As the file is uploaded to a temporary name, it is technically a new file, even though the file with target name already exists. As such:
-    * after the original file is deleted and temporary file is renamed to the original file name, you lose all attributes of the original file (such as owner and group) except for basic permissions;((For this reason WinSCP never transfers to temporary file name first, if the target file is know to be owner by another user. Note that the owner name can be detected with SFTP-4 and newer only.))+    * after the original file is deleted and temporary file is renamed to the original file name, you lose all attributes of the original file (such as owner and group) except for basic permissions;((For this reason WinSCP never transfers to temporary file name first, if the target file is know to be owned by ==another user==. Note that the owner name can be detected with SFTP-4 and newer only.))
    * while you may have permissions to overwrite the existing file, you might not have permissions to create new (temporary) file.     * while you may have permissions to overwrite the existing file, you might not have permissions to create new (temporary) file.
Line 23: Line 23:
Note that partial files can be distinguished in file panel by special [[ui_file_panel#special_files|"torn sheet" overlay icon]]. Note that partial files can be distinguished in file panel by special [[ui_file_panel#special_files|"torn sheet" overlay icon]].
-To configure transfer to temporary file name in [[scripting]], use ''-resumesupport'' switch of file transfer commands. In .NET assembly use ''[[library_transferoptions#resumesupport|TransferOptions.ResumeSupport]]''.+To configure transfer to temporary file name in [[scripting]], use ''-resumesupport'' ==switch== of file transfer commands (such as [[scriptcommand_put|''put'']], [[scriptcommand_get|''get'']], etc). In .NET assembly use ''[[library_transferoptions#resumesupport|TransferOptions.ResumeSupport]]''.
Transfer to temporary filename is supported with [[sftp|SFTP protocol]] only and only for [[transfer_mode|binary transfers]]. Transfer to temporary filename is supported with [[sftp|SFTP protocol]] only and only for [[transfer_mode|binary transfers]].
Line 30: Line 30:
There's an alternative manual method to resume transfer, which can be used with FTP protocol. There's an alternative manual method to resume transfer, which can be used with FTP protocol.
-If you attempt to transfer a file already in the target directory and the target file is smaller then the source file, the [[ui_overwrite|overwrite confirmation dialog]] displays a //Resume// command or an //Append// command (when appending is supported), in the drop·down menu of the //No// button. After you click //Append//, WinSCP opens another prompt that lets you append source file or resume your transfer.+If you attempt to transfer a file already in the target directory and the target file is smaller then the source file, the [[ui_overwrite|overwrite confirmation dialog]] displays a //Resume// command or an //Append// command (when appending is supported), in the drop-down menu of the //No// button. After you click //Append//, WinSCP opens another prompt that lets you append source file or resume your transfer.
If you resume the transfer, WinSCP will skip a part of the source file equal to the target file's size. The program will only transfer the remainder. If you resume the transfer, WinSCP will skip a part of the source file equal to the target file's size. The program will only transfer the remainder.

Last modified: by martin