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

Jump to bottom

Calculate timezone offset #1386

Closed
cyberduck opened this issue Dec 4, 2007 · 6 comments
Closed

Calculate timezone offset #1386

cyberduck opened this issue Dec 4, 2007 · 6 comments
Assignees
@dkocher
Labels
core enhancement wontfix

Comments

@cyberduck
Copy link
Collaborator

anonymous created the issue

Hi,
I'm having a date/time problem with CyberDuck 2.81. I believe that you can fix it.
When I upload a file to this certain server, the time stamp is always exactly 8 hours wrong. I believe that this is a time zone error, or the failure to take a time zone into account. I have just tested with several Mac FTP clients, and most also have this problem. But not all, so I think it's fair to assume that this is a FTP client issue. I'd really like it if this could be fixed in the next release.

I am in California, and I have named the uploaded files with my local time of uploading. I don't know where the ftp server is (but that shouldn't really matter). The files I am uploading today are all prepended with "DN-TimeTestDec3" and I was careful to get the correct time in the filename.

The winner of this little TimeZone contest was FileZilla (both Mac & Win versions), (and apparently FireFox) which actually calculated the time offset, when apparently none of the other FTP clients did. Since your FTP software needs to stay ahead of the competition, it's clear that this time calculation needs to be taken care of. I imagine it's not a complicated deal, and it would be MUCH appreciated.

I have screen photos, look at them here:

(http://nathanson.com/ftptimezoneproblem/CyberDuck281.gif)

(http://nathanson.com/ftptimezoneproblem/FileZillaMac_ShowsCorrectTime.gif)

(http://nathanson.com/ftptimezoneproblem/FireFoxWWW_showsRightTime.gif)

I also tested Transmit & Interarchy, and they also showed the wrong time. Same url as above, but swap in
InterarchyFTP.gif & TransmitFTP.gif
This web form rejects messages with "too many outgoing links".

All are the same FTP server, same files. Most show the wrong time of uploading due to an 8 hour time shift that isn't being handled correctly.

My system: Mac OSX 10.4.9 on intel iMac.

Thanks!

Hope this helps.

Best,
Dave Nathanson[[br]]
Mac Medix [[br]]
CyberDuck Donater.
@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 6, 2007 •
edited

@dkocher commented

This is a duplicate for #12362. However I do not agree this is a bug. The files displayed just show the local time of the remote server. There is no way to know the timezone difference. An enhancement might be to let the user specify the remote timezone in the bookmark setting and then adjust the date for display in the browser to the local timezone.

This is however a serious issue when synchronizing as reported in #12198.

@cyberduck
Copy link
Collaborator Author

anonymous commented

Having the same issue. However, I admin the ftp site in this case. The site's computer is set to correct time (network updated set to pst). Client upload computer is set to correct time (pst). 8 hr offset is found when uploading from one machine to another in the same office (all with the same local time settings). This is truly frustrating and has been an issue for ages. I believe that the issue is on the mac server end, not the client end but am still mystified.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [1386 anonymous]:
Filezilla does this as described in #2645.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Experimental. In 43edd3a a proposed fix has been commited. This can be enabled using

defaults write ch.sudo.cyberduck ftp.timezone.auto true

Default is false. We cannot differentiate between the raw UTC offset and the offset including daytime saving. Therefore the matched timezone is often still not correct.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone 3.2 deleted

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 dkocher]:

Experimental. In 43edd3a a proposed fix has been commited. This can be enabled using

defaults write ch.sudo.cyberduck ftp.timezone.auto true

Default is false. We cannot differentiate between the raw UTC offset and the offset including daytime saving. Therefore the matched timezone is often still not correct.

We will not change the default setting.

@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.
Assignees

@dkocher dkocher

Labels
core enhancement wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck