Differences
This shows you the differences between the selected revisions of the page.
| 2022-11-25 | 2024-10-31 (current) | ||
| Restored revision 1663576831. Undoing revisions 1669355784, 1669355899, 1669355996. (martin) (hidden) | not (martin) | ||
| Line 50: | Line 50: | ||
| The //Preserve timestamp// checkbox makes WinSCP preserve the last modification timestamp of the transferred file. Note that there are several [[timestamp|factors that can affect timestamp recalculation]] between local and remote filesystem. Check the suboption //Including directories// to preserve the last modification timestamp of the transferred directories too (This option is supported with [[SFTP]] protocol only.) | The //Preserve timestamp// checkbox makes WinSCP preserve the last modification timestamp of the transferred file. Note that there are several [[timestamp|factors that can affect timestamp recalculation]] between local and remote filesystem. Check the suboption //Including directories// to preserve the last modification timestamp of the transferred directories too (This option is supported with [[SFTP]] protocol only.) | ||
| - | Note that while you may have rights to overwrite the remote file, you may not have rights to change its timestamp. See //[[#upload|Ignore permissions errors]]//. The option is disabled when configuring transfer settings for [[task_synchronize_full|synchronization]], as preserving timestamps is mandatory then.((Unless comparison criteria //[[ui_synchronize#criteria|Modification time]]// is turned off.)) With FTP protocol, preserving timestamp of uploaded files may not be supported with old FTP servers.((Server needs to support ''MFMT'' command.)) Most WebDAV servers do not support preserving timestamps, but as the capability is not detectable, the option is available always and when enabled, WinSCP tries to preserve the timestamp and silently continues when the server fails. S3 protocol does support preserving timestamps either. | + | Note that while you may have rights to overwrite the remote file, you may not have rights to change its timestamp. See //[[#upload|Ignore permissions errors]]//. The option is disabled when configuring transfer settings for [[task_synchronize_full|synchronization]], as preserving timestamps is mandatory then.((Unless comparison criteria //[[ui_synchronize#criteria|Modification time]]// is turned off.)) With FTP protocol, preserving timestamp of uploaded files may not be supported with old FTP servers.((Server needs to support ''MFMT'' command.)) Most WebDAV servers do not support preserving timestamps, but as the capability is not detectable, the option is available always and when enabled, WinSCP tries to preserve the timestamp and silently continues when the server fails. S3 protocol does not support preserving timestamps either. |
| The //==Calculate== total size// checkbox makes WinSCP calculate total size of all files in all selected directories to be transferred before the actual transfer. It allows it then to estimate time necessary to complete the transfer. Note that if you are going to transfer large number of directories the calculation can take significant time. The option cannot be disabled for background transfers, when using [[ui_pref_background|multiple connections]]. Note that when using multiple connections, the calculation does not add time to a transfer, as directories are not listed again for the transfer itself. | The //==Calculate== total size// checkbox makes WinSCP calculate total size of all files in all selected directories to be transferred before the actual transfer. It allows it then to estimate time necessary to complete the transfer. Note that if you are going to transfer large number of directories the calculation can take significant time. The option cannot be disabled for background transfers, when using [[ui_pref_background|multiple connections]]. Note that when using multiple connections, the calculation does not add time to a transfer, as directories are not listed again for the transfer itself. | ||