remote timestamp is 1 hr too big (v. 5.2.5 beta)

Hello!

WinSCP shows all remote timestamps 1 hr larger than
a) local upload time
b) timestamps shown with command line ftp dir
c) other FTP program.
I attached a screenshot of the WinSCP screen and a command-line-FTP-dir-screen.
Also I attached a log-level-1-file, which does not contain much, as I did only open the connection to look at the file listing.

This is probably why autosync doesnt work.

Thanks for your good work.

Dominik

My system is XP Pro SP3.

This is just hours before DST is ending, so I'll check the issue tomorrow again.

When i go to the provider-supplied web-ftp interface, i see the same modification times as in command line ftp and locally, i.e. i see summer time values.

Maybe WinSCP interprets the time stamps from the server as in standard time, while really it is in summer time, and "corrects" this by adding an extra hour. Just a thought.

yours

Dominik

It seem in fact connected to DST. For the time beeing, it won't come back until spring next year.

What particular file should I look at in the log/screenshots?

Also did you read this?
https://winscp.net/eng/docs/timestamp#windows

Hello,

you can look at any file. Every file in the remote-window of WinSCP had a timestamp exactly 1 h "later" than in the windows-command-line-FTP-dir-window.

In the log, every file has its correct UTC timestamp, as it should have according to https://datatracker.ietf.org/doc/html/rfc3659#section-2.3 .

Windows displays the time modified according to the actual time zone setting, which was gmt+2 (now is gmt+1).

Somehow WSCP displayed gmt+3 during daylight saving time for the "remote" window.

May be its a strange error occurring at the last day of dst...

HTH

Dominik

PS: Yes I have read the page You mentioned.

dominik wrote:

May be its a strange error occurring at the last day of dst...

So it was not happening in the days before?

I could work smoothly for several months. Before oct 26th I did not use the program for 10 days or so, so I cannot say for sure whether the issue arises _only_ on that special day.

I did not check the timestamps though, because everything went fine. I used to work with the command line and start WinSCP with autostart to save routine work - a very useful feature, thanks for that. Only when it stopped working, I switched over to GUI and saw the timestamp issue.

Also since then it is working well, so there is no need to hurry - only it is interesting.

Ok, thanks for all the information.