Differences
This shows you the differences between the selected revisions of the page.
| 2016-01-22 | 2017-01-18 | ||
| library_transferoptions#resumesupport (martin) | broken_connection explicit anchor (martin) | ||
| Line 43: | Line 43: | ||
| If the target file exists and it is not write-able, but the target directory is, the file will may be transferred anyway with automatic resume. The error overwriting the file will occur only after the transfer finishes. It is because the file is first transferred into temporary file. | If the target file exists and it is not write-able, but the target directory is, the file will may be transferred anyway with automatic resume. The error overwriting the file will occur only after the transfer finishes. It is because the file is first transferred into temporary file. | ||
| - | ===== Resuming from Broken Connections ===== | + | ===== [[broken_connection]] Resuming from Broken Connections ===== |
| With [[sftp|SFTP]] and [[ftp|FTP]] protocols, when connection is broken, WinSCP can automatically reconnect and resume the transfer((If transfer resuming/transfer to temporary files name is disabled, file transfer will start from the beginning, with [[sftp|SFTP protocol]].)). This can be configured on //[[ui_pref_resume|Endurance page]]// of Preferences dialog. | With [[sftp|SFTP]] and [[ftp|FTP]] protocols, when connection is broken, WinSCP can automatically reconnect and resume the transfer((If transfer resuming/transfer to temporary files name is disabled, file transfer will start from the beginning, with [[sftp|SFTP protocol]].)). This can be configured on //[[ui_pref_resume|Endurance page]]// of Preferences dialog. | ||