Topic "Timestamp problem on remote FTP (FTPS)"

Author Message
PaJi
[View user's profile]

Joined: 2011-08-16
Posts: 1
Location: CZ
Hi Martin,

I "discovered" known problem, but therefore I can't use your program which seems me very nice.

Problem is in the remote timestamp on FTP by the synchronization. All valids for FTPS (TLS) version and for pure FTP connection.


Conditions:
*************

OS: Tested on more computers:
-------------------------------
- Win2008 R2 SP1 Eng
- Win7 SP1 Cze
- Win2000 SP4 Cze

WinSCP:
---------
- Version 4.3.4
- ALL valids both modes - interactive and scripting.

FTP(s) Server - NAS:
----------------------
- 220 ProFTPD 1.3.3c Server (NETGEAR ReadyNAS)
- It supports FTP and FTPS (over TLS) only. I would like to use FTPS.
- Look bellow on the part of the connection log.


I tried to synchronize File1.txt and File2.txt.

Local (stored on NTFS disk, once on FAT32):
---------------------------------------------
File1.txt 2011-08-10 15:30
File1.txt 2011-08-10 20:30

Remote (ReadyNAS FTPS)
-----------------------
File1.txt 2011-08-10 13:30
File1.txt 2011-08-10 18:30

These wrong list I get from WinSCP 4.3.4 (interactive and script). In Total Commander's FTP client I get properly timestamp in pure FTP mode. Same on both sides 15:30 and 20:30.


Result (is it bug?):
======================
It seems me - for remote FTP (FTPS - TLS) properties is missed the back translation for the timestamp if you load any information from FTP. The timestamp on FTP is in UTC format stored. I watched the log and there is the command MFMT to set UTC timestamp after putting the file into FTP. Any FTP servers return UTC timestamp (timestamp which is stored), any servers translate stored timestamp into local time. ReadyNAS returns stored timestamp till this time.
I think it should be some checkbox (translate back) or


Solutions - suggest:
======================
It should be possible for ALL TYPES of the connections:
---------------------------------------------------------

1) Store to remote system FTP(s):
-----------------------------------
a) Store in UTC timestamp
b) Store in UTC timestamp include Daylight
c) Store in Local timestamp (independent of Daylight)
d) Store in Local timestamp include Daylight


2) Load from remote system FTP(s):
------------------------------------
a) No convert
b) No convert but include Daylight
c) Convert to Local convention (independent of Daylight)
d) Convert to Local convention include Daylight


3) Difference:
----------------
The possibility to set the difference time-window (for example from 0 till 999 hours = cca 40 days). The time should have the minutes too. If the absolute difference between the timestamps will be in the interval, then take the timestamps of both files like the equal.

All these possibilities should be accessible by all type of connections. A lot of the servers know FTP (FTPs) only!! Sure with this third option the online synchronization can be disabled, but it is not need.

I don't know, but I think a lot of people use synchronization like the "backup". In this case the third option seems me very helpful. (For example to set the interval 2,5 hours in CZ = avoiding a lot of problems with timestamp translations).

Thanx.

PaJi
-----------


Connecting to x.x.x.x ...
. 2011-08-16 12:06:28.532 Connected with x.x.x.x, negotiating SSL connection...
< 2011-08-16 12:06:28.532 220 ProFTPD 1.3.3c Server (NETGEAR ReadyNAS) [x.x.x.x]
> 2011-08-16 12:06:28.532 AUTH TLS
< 2011-08-16 12:06:28.548 234 AUTH TLS successful
. 2011-08-16 12:06:28.813 SSL connection established. Waiting for welcome message...
> 2011-08-16 12:06:28.813 USER MyUser
< 2011-08-16 12:06:28.813 331 Password required for MyUser
> 2011-08-16 12:06:28.813 PASS ***********
< 2011-08-16 12:06:28.813 230 User MyUser logged in
> 2011-08-16 12:06:28.813 SYST
< 2011-08-16 12:06:28.813 215 UNIX Type: L8
> 2011-08-16 12:06:28.813 FEAT
< 2011-08-16 12:06:28.813 211-Features:
< 2011-08-16 12:06:28.813 MDTM
< 2011-08-16 12:06:28.813 MFMT
< 2011-08-16 12:06:28.813 TVFS
< 2011-08-16 12:06:28.813 AUTH TLS
< 2011-08-16 12:06:28.813 MFF modify;UNIX.group;UNIX.mode;
< 2011-08-16 12:06:28.813 MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
< 2011-08-16 12:06:28.813 LANG en-US*
< 2011-08-16 12:06:28.813 PBSZ
< 2011-08-16 12:06:28.813 PROT
< 2011-08-16 12:06:28.813 SITE MKDIR
< 2011-08-16 12:06:28.813 SITE RMDIR
< 2011-08-16 12:06:28.813 SITE UTIME
< 2011-08-16 12:06:28.813 SITE SYMLINK
< 2011-08-16 12:06:28.813 REST STREAM
< 2011-08-16 12:06:28.813 SIZE
< 2011-08-16 12:06:28.813 211 End
> 2011-08-16 12:06:28.813 PBSZ 0
< 2011-08-16 12:06:28.813 200 PBSZ 0 successful
> 2011-08-16 12:06:28.813 PROT P
< 2011-08-16 12:06:28.813 200 Protection set to Private
. 2011-08-16 12:06:28.813 Connected
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 25034
Location: Prague, Czechia
You can set the timezone offset on login dialog:
https://winscp.net/eng/docs/ui_login_environment#timezone_offset

Also this request has been added to the tracker:
https://winscp.net/tracker/show_bug.cgi?id=714
_________________
Martin Prikryl
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License