Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File dates don't seem to be converted properly #1830

Closed
cyberduck opened this issue Mar 2, 2008 · 1 comment
Closed

File dates don't seem to be converted properly #1830

cyberduck opened this issue Mar 2, 2008 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 2, 2008

885120a created the issue

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 21, 2008

@dkocher commented

#12198.

Loading

@cyberduck cyberduck closed this Jul 21, 2008
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants