Re: Timestamp not working properly when DST is in effect?
Please read FAQ. If that does not help, come back.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Guest
I forgot to mention that both systems are running Windows XP. The local one Home (SP3), the remote Pro (SP3). Both have the latest updates from Microsoft applied.
- Guest
Timestamp not working properly when DST is in effect?
I am transferring a file to a remote server via and the timestamp for the file on the server is off by 1 hour. Both systems are set for (GMT-05:00) Eastern Time (US & Canada) and "Automatically adjust clock for daylight saving changes" is checked.
On the local system the file shows as having a timestamp of Jun 4, 2009, 3:09pm. The remote system shows the same date with a time of 2:09pm
If I set the local time zone to (GMT) Greenich Mean Time, the timestamp shown in explorer on the local machine is 7:09pm. The XML log for the transfer shows the following:
<touch>
<filename value="/fromRemote/backup.db3" />
<modification value="2009-06-04T18:09:27.000Z" />
<result success="true" />
</touch>
Shouldn't the value be ="2009-06-04T19:09:27.000Z"?
Files that have timestamps where DST is not in effect (e.g. Feb 4, 2008, 5:28pm) appear to have the correct timestamp on the remote system.
I am currently using WinSCP 4.2.1 (build 428), but this happened for 4.1.8 and 4.1.9 as well.
The remote machine is running freeFTPd version 1.0.11
byngl at users dot sourceforge dot net
On the local system the file shows as having a timestamp of Jun 4, 2009, 3:09pm. The remote system shows the same date with a time of 2:09pm
If I set the local time zone to (GMT) Greenich Mean Time, the timestamp shown in explorer on the local machine is 7:09pm. The XML log for the transfer shows the following:
<touch>
<filename value="/fromRemote/backup.db3" />
<modification value="2009-06-04T18:09:27.000Z" />
<result success="true" />
</touch>
Shouldn't the value be ="2009-06-04T19:09:27.000Z"?
Files that have timestamps where DST is not in effect (e.g. Feb 4, 2008, 5:28pm) appear to have the correct timestamp on the remote system.
I am currently using WinSCP 4.2.1 (build 428), but this happened for 4.1.8 and 4.1.9 as well.
The remote machine is running freeFTPd version 1.0.11
byngl at users dot sourceforge dot net