Opened 13 years ago

Last modified 6 years ago

#1197 closed Bug report

Year bug

Reported by: exoloner Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc: exoloner, Tim Kosse, rkodey, Alexander Schuch
Component version: Operating system type:
Operating system version:

Description

As searching in summary and resulting in 0 matches concerning this bug, I'm going to postit:

under windows server 2003 and Filezilla server v 0.9.20

all downloaded files appears with CurrentYear-1 in datetime file properties in ALL windows OSes

It's like FileZilla decrements the year number in one??

Attachments (4)

shoot_FileZilla_YearBug.gif (84.6 KB) - added by exoloner 12 years ago.
screenshoot showing the recently uploaded file, shows altered date-year info on the client side,
shoot_FileZilla_YearBug.2.gif (84.6 KB) - added by exoloner 12 years ago.
screenshoot showing the recently uploaded file, shows altered date-year info on the client side,
BUGGY1.rtf (11.5 KB) - added by exoloner 12 years ago.
trace of FZserver, a readme.txt file has been uploaded using the filezilla CLIENT
BUGGY2.rtf (11.8 KB) - added by exoloner 12 years ago.
trace of FZserver, a abrash.pdf file has been uploaded using the Windoze ftp CLIENT.

Download all attachments as: .zip

Change History (19)

comment:1 Changed 13 years ago by Tim Kosse

What client are you using? Are the clocks on both the client and the server systems synchronized?

comment:2 Changed 13 years ago by exoloner

Yes, here it is the procedure that generates the bug.
Windows 2000, SP4
we open a file explorer, and type in our FTp server address.
Upload a file.
Pressing F5 to refresh the dir. listing.
Ooops!!! the recently uploaded file appears 1 year old
now, try to download that file
Oops!! we downloaded it with wrong year!!

One interesting thing is that, when we inspect the file using a UNC smb url like
server\sharedFTPfolder the files datetime appears normally ok. (our server is windows server 2003 SP1)

It's like filezilla giving wrong year response, when asked to do a LIST operation over files uploaded with windows file explorer on Windows 2000 ?????

comment:3 Changed 12 years ago by rkodey

This is still a bug in 3.0.1 client. Server is ProFTPD 1.3.0a on Linux. It appears to be related to timezones. The year is incorrect between the times of midnight GMT, and when the local timezone reaches midnight. (It's happening for Eastern time, anyway.)

Changed 12 years ago by exoloner

Attachment: shoot_FileZilla_YearBug.gif added

screenshoot showing the recently uploaded file, shows altered date-year info on the client side,

comment:4 Changed 12 years ago by exoloner

File Added: shoot_FileZilla_YearBug.gif

Changed 12 years ago by exoloner

screenshoot showing the recently uploaded file, shows altered date-year info on the client side,

comment:5 Changed 12 years ago by exoloner

http://www.threepixels.org/misc/shoot_FileZilla_YearBug.gif

as you can see, we have our server at 192.168.0.1

our client at 192.168.0.13, we uploaded that marked file, then
we reconnect, and the ftp-windows client is coming-up with a
wrong year, you'll see 2006.

So :
FileZilla server, is working badly on windows, and hacking the filesystem datetime info of the uploaded files?
Both SOs are WinXP pro with SP2
File Added: shoot_FileZilla_YearBug.gif

comment:6 Changed 12 years ago by rkodey

Per my previous comment, the problem is also happening with ProFTPD 1.3.0a on Linux. So, I believe it's a client bug, not a server one.

Please re-categorize this as a client bug.

I've also done some more tests, and an fairly sure it's a timezone problem. I'm in EST, and the file dates are only incorrect if I upload them between the 4 hours between midnight GMT and midnight localtime. Further, the incorrect dates magically correct themselves after midnight localtime.

comment:7 Changed 12 years ago by exoloner

"Please re-categorize this as a client bug."
note: When the server side uses a MS IIS ftp server, that problem does not appear.

So yes, can we speak about a client side trouble? and being more accurate :

FileZilla server is incompatible with all (thousands of them) microsoft ftp clients.

so, actually we don't know nothing about this phenomena.
Can we have a look at the timestamp file attributes saving code of our FileZillaServer?
Perphaps this can show us the path to solve the mistery.

comment:8 Changed 12 years ago by exoloner

"Please re-categorize this as a client bug."
note: When the server side uses a MS IIS ftp server, that problem does not appear.

So yes, can we speak about a client side trouble? and being more accurate :

FileZilla server is incompatible with all (thousands of them) microsoft ftp clients.

so, actually we don't know nothing about this phenomena.
Can we have a look at the timestamp file attributes saving code of our FileZillaServer?
Perphaps this can show us the path to solve the mistery.

comment:9 Changed 12 years ago by Tim Kosse

Please try FileZilla client, enable "Show raw directory listing" in the settings dialog and attach the contents of the message log.

In addition, what's your local timezone.

Changed 12 years ago by exoloner

Attachment: BUGGY1.rtf added

trace of FZserver, a readme.txt file has been uploaded using the filezilla CLIENT

comment:10 Changed 12 years ago by exoloner

File Added: BUGGY1.rtf

Changed 12 years ago by exoloner

Attachment: BUGGY2.rtf added

trace of FZserver, a abrash.pdf file has been uploaded using the Windoze ftp CLIENT.

comment:11 Changed 12 years ago by exoloner

File Added: BUGGY2.rtf

comment:12 Changed 12 years ago by exoloner

yes, my GMT is +01:00

I've uploaded to this thread , 2 RTF log files (with tracing, and raw time format. hope it helps.

I'm noticing _again_ the (-1) in the year, when listing dir. contents, within a Micro$oft ftp Client.

I didn't really care about that, I use FZclient, but there are thousands of dummy people-customers out there
using that FTP client crap!! from m$. Is not comprehensible for them, you have to wait 6 hours to see that year correctly in *THAT* client.

Is FileZilla Server doing something wrong, or understandable for all those ms ftp clients?.

Thanks

comment:13 Changed 12 years ago by Tim Kosse

From the log: "Trace: -rwxr-xr-x 1 ftp ftp 3331425 Sep 23 15:00 deathout.exe"

It doesn't even contain a date, so it's not the fault of FileZilla Server.

comment:14 Changed 12 years ago by rkodey

I'm GMT -0400 (FileZilla Client 3.0.1)

Here's snapshot #1, being done at 11:03pm Eastern 9/24 (aka GMT 03:03 9/25)

Response: 220 ProFTPD 1.3.0a Server
Command: SYST
Response: 215 UNIX Type: L8
Command: LIST -a
Response: 150 Opening ASCII mode data connection for file list
Listing: drwxr-x--x 2 user1103899 user1103899 4096 Sep 25 03:03 .
Listing: drwxr-x--x 8 user1103899 user1103899 4096 Apr 18 17:39 ..
Listing: -rw-r--r-- 1 user1103899 user1103899 1362 Sep 25 03:03 cache.xml
Response: 226 Transfer complete.
Status: Directory listing successful

The resulting "Last Modified" date shown in FileZilla Client is:
cache.xml 9/24/2006 11:03:00 PM

So, notice it's done the timezone conversion properly for the time, and day of the month. However, the year has been decremented somehow.

I'll do another snapshot just past midnight, so you can see the exact same file correct itself in the Client.

comment:15 Changed 12 years ago by Alexander Schuch

rkodey posted the bug separately already, so in case the "other" issue is solved, this one can be closed.

[ 1801756 ] Timezone conversion error - incorrect year

Note: See TracTickets for help on using tickets.