You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens on 2 different hosting companies, so I believe it's a Cyberduck bug, not a hosting company bug.
If I upload a file, the modification date on the server gets converted incorrectly. It acts as if the date is changed to UTC but stored on the server in the server's local time. The result of this is that if I synchronize, modify a file locally, and synchronize again, Cyberduck thinks the file should be downloaded instead of uploaded. In the Transfers detail section, the timestamp on the remote file will show as 8 hours in the future, while the timestamp on the local file shows the correct date and time.
The text was updated successfully, but these errors were encountered:
This happens on 2 different hosting companies, so I believe it's a Cyberduck bug, not a hosting company bug.
If I upload a file, the modification date on the server gets converted incorrectly. It acts as if the date is changed to UTC but stored on the server in the server's local time. The result of this is that if I synchronize, modify a file locally, and synchronize again, Cyberduck thinks the file should be downloaded instead of uploaded. In the Transfers detail section, the timestamp on the remote file will show as 8 hours in the future, while the timestamp on the local file shows the correct date and time.
The text was updated successfully, but these errors were encountered: