SFTP Preserve Time in SSH Not Honored

Hello,

Thank you for reporting this.

I was able to confirm that the Preserve timestamps when downloading/uploading setting is currently not available for the side-pane SFTP used within an SSH session. At this time, there is no option in the SSH entry configuration to enable timestamp preservation specifically for the integrated SFTP pane.

Since this capability is not currently implemented, we will consider this a feature request for our development team to evaluate in a future release.

Best regard

Hello,

I've opened a ticket so we can add this.

Regards,

Thanks both. I am encountering a similar albeit different issue - moving the same file more than once does not preserve time stamp after the first copy.

I tried this both letting RDM overwrite, manually deleting it from within the SFTP session in RDM first, and rm from Debian via parallel ssh before copying. All the same result.

This one definitely falls as bug vs request!

Further, dragging the same file into another folder for the first time still preserves the time stamp. But a new file dragged right after keeps its metadata. This time I did not rm it, but just overwrote it from the SFTP session:

Hello,

Just to confirm, in this case, it's specifically with the SFTP session and not with the SSH terminal using the SFTP side-panel? Since, from what I understand, the SFTP side-panel never preserves timestamps at the moment.

Regards,

Hello,

Just to confirm, in this case, it's specifically with the SFTP session and not with the SSH terminal using the SFTP side-panel? Since, from what I understand, the SFTP side-panel never preserves timestamps at the moment.

Regards,

@Hubert Mireault
That is correct. In a dedicated SFTP session!

Thank you for the confirmation. I've played a bit with the entry and there seems to be a few cases where the timestamp does not get preserved despite the setting being enabled. Namely, even with just a simple upload, it doesn't seem to preserve it, which sounds like the primary use case of the setting failing, even without getting into the multiple copy scenarios you mentioned.

I've opened a ticket so we can investigate this further.

Regards,