Opened 15 years ago

Closed 15 years ago

#4116 closed Bug report (rejected)

Last modified cuts off seconds

Reported by: shaw10 Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: Vista SP1


Last modified changes seconds to 00 instead of the actual value. I don't know if this is a limitations of the server, although MTDM does return all the seconds.

So am I correct to say that if you wanted to show the entire last modified you would have to do a MTDM for each file?

Shouldn't FileZilla use MTDM to find the last time the file was modified and use that date/time for the local file date/time when you download files. It currently doesn't seem to do this. I end up with last modified files of XX/XX/XXXX XX:XX:00XX

Log of file download with preserve timestamps enabled.

00:06:15 Status: Connecting to .*.*.:21...
00:06:15 Status: Connection established, waiting for welcome message...
00:06:15 Response: 220 Microsoft FTP Service
00:06:15 Command: USER *
00:06:15 Response: 331 Password required for *.
00:06:15 Command: PASS
00:06:17 Response: 230-FTP-SSL (AUTH TLS, Explicit FTPS or FTPES) security is available
00:06:17 Response: 230 User logged in.
00:06:17 Command: SYST
00:06:17 Response: 215 Windows_NT
00:06:17 Command: FEAT
00:06:17 Response: 211-Extended features supported:
00:06:17 Response: LANG EN*
00:06:17 Response: UTF8
00:06:17 Response: AUTH TLS;TLS-C;SSL;TLS-P;
00:06:17 Response: PBSZ
00:06:17 Response: PROT C;P;
00:06:17 Response: CCC
00:06:17 Response: HOST
00:06:17 Response: SIZE
00:06:17 Response: MDTM
00:06:17 Response: 211 END
00:06:17 Command: OPTS UTF8 ON
00:06:17 Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
00:06:17 Status: Connected
00:06:17 Status: Retrieving directory listing...
00:06:17 Command: CWD /
00:06:18 Response: 250 CWD command successful.
00:06:18 Command: PWD
00:06:18 Response: 257 "/" is current directory.
00:06:18 Command: TYPE I
00:06:18 Response: 200 Type set to I.
00:06:18 Command: PASV
00:06:18 Response: 227 Entering Passive Mode (
00:06:19 Command: LIST
00:06:19 Response: 125 Data connection already open; Transfer starting.
00:06:19 Response: 226 Transfer complete.
00:06:19 Command: PASV
00:06:19 Response: 227 Entering Passive Mode (,*,*,,*,131).
00:06:19 Command: LIST -a
00:06:20 Response: 125 Data connection already open; Transfer starting.
00:06:20 Response: 226 Transfer complete.
00:06:20 Status: Calculating timezone offset of server...
00:06:20 Command: MDTM configuration.asp
00:06:21 Response: 213 20081228061510
00:06:21 Status: Timezone offsets: Server: -25200 seconds. Local: -21600 seconds. Difference: 3600 seconds.
00:06:21 Status: Directory listing successful
00:09:01 Status: Starting download of /configuration.asp
00:09:01 Command: PASV
00:09:01 Response: 227 Entering Passive Mode (
00:09:01 Command: RETR configuration.asp
00:09:02 Response: 125 Data connection already open; Transfer starting.
00:09:02 Response: 226 Transfer complete.
00:09:02 Status: File transfer successful

Remote Last modified 12/28/2008 12:15:00AM
Local Last modified 12/28/2008 12:15:00AM

Notice the actual time: 12/28/2008 06:15:10 AM UTC

I am -6 GMT. Server is Mountain Standard Time with no Daylight Saving Time -7 GMT.

The display I don't really care about, but for downloads, I have software that uses the last modified time. If its different it automatically makes a backup of it. I could configure it to use checksums, but in the past that has taken too much time.

If you could please look into this I would greatly appreciate it.

Thank you,


Change History (1)

comment:1 by Tim Kosse, 15 years ago

Resolution: rejected
Status: newclosed

The listing returned by LIST does not have the seconds. Using MDTM on every single file would be far too slow.

Note: See TracTickets for help on using tickets.