Opened 12 years ago

Last modified 5 years ago

#1238 closed Bug report

Incorrect year displayed

Reported by: banquero Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: banquero, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Filezilla client connecting to AIX server via secure FTP shows the wrong year (2006) on certain files and directories. Those files and directories were created when the system date was rolled to test DST (from 02/27/2007:14:05:00 to 3/11/2007:01:00:00). The time then rolled at 01:59:59 to 03:00:00. Files created previous to DST rollover still show correct year. New directories dated after date/time was rolled back (to 02/27/2007:{current_time}), show the correct year if some files in it have a 2007 year (because files/directories were created before the DST time change).

An earlier reported bug may be related (1608370 "Year bug") but is not the same. When files are seen via another FTP client ("SecureFX") or with another telnet program ("PuTTy" or "SecureCRT" terminal), the year IS correct. So far, only Filezilla shows the anomaly.

Attachments (4)

Filezilla problem.JPG (187.4 KB) - added by banquero 12 years ago.
Two snapshot of same directory with wrong and right year.
Filezilla Directory Cache Dump.txt (8.5 KB) - added by banquero 12 years ago.
Here is the "Dump Directory Cash" output from the "Debug" menu item.
Filezilla problem.log (16.1 KB) - added by banquero 12 years ago.
Trace log file
Filezilla problem 3.jpg (178.0 KB) - added by banquero 12 years ago.
Snapshot showing both trace and display of directories

Download all attachments as: .zip

Change History (12)

Changed 12 years ago by banquero

Attachment: Filezilla problem.JPG added

Two snapshot of same directory with wrong and right year.

comment:1 Changed 12 years ago by Tim Kosse

Please post a log with enabled "Show raw directory listing" as well as the exact date/time the log was created.

Changed 12 years ago by banquero

Here is the "Dump Directory Cash" output from the "Debug" menu item.

comment:2 Changed 12 years ago by banquero

Apparently, I can only attach one snapshot at a time. I'll be submitting updates for subsequent files. Notice the dates on directories named 2007-Mar-01 through 10 and one named 2007-Feb-26. The next file will show that the Trace contains 2007 as the year not 2006 as displayed.
File Added: Filezilla Directory Cache Dump.txt

Changed 12 years ago by banquero

Attachment: Filezilla problem.log added

Trace log file

comment:3 Changed 12 years ago by banquero

Here is the Trace log file. I was incorrect before when I stated that it would show the correct year (2007). However, the date format infers that the directories in question are from this year and not from 2006. The log files were created on 3/1/2007.
File Added: Filezilla problem.log

Changed 12 years ago by banquero

Attachment: Filezilla problem 3.jpg added

Snapshot showing both trace and display of directories

comment:4 Changed 12 years ago by banquero

The second graphic shows the trace stream above and the display of the directories. The directories names in the format "YYYY-Mmm-DD" (generated on 3-11-2007) are generated from the system time and therefore should not show a previous year. The PuTTy display shot from earlier shows those directories with the right year displayed.
File Added: Filezilla problem 3.jpg

comment:5 Changed 12 years ago by Tim Kosse

Won't fix.

The listing format used by the server displays the time for files younger than one year, on older files it displays the year instead. As result, the client has to reconstruct the year in case the time gets sent.

Problems:

  • Cutoff distance between time and year unknown As result, files with a timestamp from the future and with given time cannot always be assigned correct year
  • Server and client time not synchronized
  • Different timezones.

comment:6 Changed 12 years ago by banquero

Why is it that SecureFX and other FTP programs are able to "reconstruct" the date correctly or at least not show the wrong date (specifically the year)? Only the year is off, the month, day and time are correct. Is Filezilla not DST complient?

comment:7 Changed 12 years ago by Tim Kosse

The listing format has not been standardized and leaves much room for interpretation.

From the information given in the log, FileZilla does the right thing.

comment:8 Changed 12 years ago by banquero

So, the consensus is that there's nothing to fix? Does it mean that if "FileZilla does the right thing", the right thing means displaying the wrong year? What does it mean that the "listing format has not been standardized"? Does that refer to the layout, the calculation of dates? Is that just for FileZilla or is that an industry-wide non-standardization? If FileZilla does "the right thing", why don't other FTP programs follow suit or lead the way displaying the wrong year? I'm sincerely asking because I'm not an expert programmer. In the end, what's important is that the user can ascertain accuracy. I was concerned about deleting files and directories I thought were old when in reality they weren't.

Note: See TracTickets for help on using tickets.