Tools

File creation or date modified is not the same between client and Serv-U server via FTP on File Explorer

A situation where the date modified of the file differs from the server via FTP on File explorer.

First published date

7/20/2020 9:11 AM

Last published date

7/20/2020 9:11 AM

Overview

It's a well-known Windows behavior, which was discovered a long time ago in older Windows versions (e.g., Windows 7), and it is still actual. This behavior can only be observed when using Windows file explorer for FTP connections and file transfer, but usually never happens when using FTP clients like FileZilla, WinSCP or similar.

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

The root cause of such a strange Windows file explorer's behavior is that it never sends MDTM command to Serv-U after uploading a file or refreshing file explorer's window. This command originates in UNIX and lets you query the server for the modification date and time of a file or directory. Unlike UNIX, the Serv-U FTP also enables the client to set the modification date and the time of the data on the server when the user has sufficient access rights.

It is useful in synchronizing uploaded files with those on the client. Normally, the FTP gets the date the files were created on the server and has no way to explicitly set the date of the uploaded files. The MDTM lets the client change that so they get the date of the original file on the server. It also works for directories.

Serv-U can accept the MDTM FTP command, but Windows file explorer doesn't send it after the file was uploaded or file explorer window was refreshed.

Resolution

A workaround for this situation - copy the remote URL address and use IE browser(version 9 or higher) to view the same folder, you will see the correct file timestamps.