Opened 5 months ago

Closed 5 months ago

#12603 closed Bug report (rejected)

file date from remote not recognized

Reported by: jean-paul LAMONTRE Owned by:
Priority: normal Component: FileZilla Client
Keywords: file update date Cc: jean-paul LAMONTRE
Component version: filezilla 3.57.0 Operating system type: Windows
Operating system version: win 10 version 21h2

Description

in the list of files or directories retrieved from the remote server, the date is sometimes not displayed correctly : a file changed 2021-12-01 is displayed 2021-01-12.

this creates download mistakes when I choose replace when newer

FileZilla Client


Version: 3.57.0

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2021-12-10
Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110
Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.0.6
SQLite: 3.35.5
GnuTLS: 3.7.2

Operating system:

Name: Windows 10 (build 19043), 64-bit edition
Version: 10.0
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq rdrnd lm
Settings dir: C:\Users\jean-paul\AppData\Roaming\FileZilla\

Attachments (1)

filezilla bug report - file date from remote not recognized.txt (11.2 KB ) - added by jean-paul LAMONTRE 5 months ago.
filezilla trace + output of LIST command + detazils on the problem

Download all attachments as: .zip

Change History (2)

by jean-paul LAMONTRE, 5 months ago

filezilla trace + output of LIST command + detazils on the problem

comment:1 by Tim Kosse, 5 months ago

Resolution: rejected
Status: newclosed

Ambiguous date formats cannot be parsed reliably. If you see 01/02/03 there are 6 possible date formats, all of which are used by at least one server in the world. You cannot possibly please everyone.

You must update to a more modern server supporting MLSD. The output of MLSD does not have such ambiguities.

Note: See TracTickets for help on using tickets.