FEAT isCommand: FEAT
Response: 211-Extensions supported:
Response: MDTM
Response: MFMT
Response: SIZE
Response: MLSD
Response: PASV
Response: EPSV
Response: UTF8
Response: 211 End
Status: Connection closed by server
When filtering for ftp-data, Wireshark shows for the majority of files that the server sends just the date without time, but for files from the current year, it replaces the year by the hour and minute (in local time):
-rw-r--r-- 0 mobile mobile 937004 Jul 19 2015 Helios MiniVent M1.pdf\n
-rw-r--r-- 0 mobile mobile 580975 Apr 12 14:23 Helios Service Checkliste M1.pdf\n
The time sent (14:23) is already local (CES with DST at that date), but FFS seems to interpret the time as UTC and adds 2 more hours, showing 16:23:00.
When I access the server with FileZilla, Wireshark shows the following response:type=file;size=937004;modify=20150719153735; Helios MiniVent M1.pdf\n
type=file;size=580975;modify=20190412122330; Helios Service Checkliste M1.pdf\n
These are full UTC timestamps including hour, minute, and second.
So the question is what is the difference in the requests so that the server sends different responses for FreeFileSync and FileZilla.
After the CWD command, FFS uses the LIST command, but FZ uses the MLSD command. This explains the different responses (see also here: https://stackoverflow.com/questions/40321519/ftp-server-directory-listing-formats).
Would it be possible that FreeFileSync uses MLSD if it is listed with the FEAT command (and LIST otherwise)?
]]>