Timezone difference being applied when it shouldn't be.

mdyrhaug · Post by **mdyrhaug** » Fri Mar 05, 2010 1:49 am

I am using build #1643 and downloading a file from Debian to Windows.

I have the 'do not use MDTM' option UNCHECKED, so I would expect the timestamp of my transferred file to be the same as the modified timestamp on the server.

My server time has a local time of GMT -6. So, when I log into my server and do the date command, it correctly reports the time and timezone.

When I connect using CORE FTP PRO, it shows the correct times on my server, in the local time. However, when I do my download, it seems that CORE FTP PRO is taking ANOTHER -6 hours off of the MDTM time.

If I play with the +/- hours option, then all of the times on my server are off by that much, and I don't want that either.

Selecting the GMT option, also throws all of my times off.

CORE FTP seems to be getting confused about my timezone and is trying to apply the difference even though it has already been applied.

Any Suggestions? Is this a bug?

avanchura · Post by **avanchura** » Fri Mar 12, 2010 2:34 pm

i am having the same problem.

how do i tell coreftp to NOT screw with the timestamp after uploading to the server? I want the time uploaded to be reflected at the server with the server's timestamp!

mdyrhaug · Post by **mdyrhaug** » Tue Mar 16, 2010 3:43 am

This problem is somehow related to GMT and TimeZones. After the recent time-change, my transfers are now off 5 hours (GMT to Central Time) instead of the 6 hour differences last week.

I want to point out that I have the 'do not use MDTM' option UNCHECKED, so I would expect the timestamp of my transferred file to be the same as the modified LOCAL timestamp on the server. But it is not.