I have yet another timestamp problem when synchronizing local files to a IIS 7.5 FTP server, client and server in UTC+01 with DST.
When I synchronize with a regular FTP Site, everything works fine.
When synchronizing with an FTP site using virtual host names, timestamps are correctly displayed, but when uploading a new file, the timestamp on the server and displayed in Beyond compare is 2 hours off (2 hours older than it should be). I did test this on the same server, restarting ftp services and beyond compare.
The problem seems to be in the MDTM command issued: For the same file, BC uses the following command to synchronize with a standard FTP site:
with the ftp site using a virtual host name it's
As far as I understand, this command should always send the local file's UTC time, independently of the server's time zone.
I tried unsuccessfully various timezone settings in the FTP Profiles settings.
Is there some way to deactivate server timezone detection, or any other workaround? Is this a known problem?
When I synchronize with a regular FTP Site, everything works fine.
When synchronizing with an FTP site using virtual host names, timestamps are correctly displayed, but when uploading a new file, the timestamp on the server and displayed in Beyond compare is 2 hours off (2 hours older than it should be). I did test this on the same server, restarting ftp services and beyond compare.
The problem seems to be in the MDTM command issued: For the same file, BC uses the following command to synchronize with a standard FTP site:
Code:
MDTM 20120724143520 file.txt
Code:
MDTM 20120724123520 file.txt
I tried unsuccessfully various timezone settings in the FTP Profiles settings.
Is there some way to deactivate server timezone detection, or any other workaround? Is this a known problem?
Comment