You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I noticed that Cyberduck does not list specific files on my home ftp server.[[br]]
I found that every file which is not listed has the date of "02/29/2004" as its timestamp.
Ordinary ftp servers (including ftpd of Mac OS X) return timestamp in a result of ls command, like:[[br]]
"-rw------- 1 masui masui 3147470848 Feb 29 2004 afo.mpg"
However, some ftp servers do not show year part of timestamp in directory listings, like:[[br]]
"-rwxr--r-- 1 owner 2487305280 Feb 29 12:00 bfo.mpg"
My home ftp server software is latter one. Is that a defect of the software?
When a file which has timestamp of "02/29/2004 12:00" (see "bfo.mpg" above) exists on the server,[[br]]
Cyberduck treats that information as "02/29/2007 12:00" because the server does not report year part[[br]]
of the timestamp. I think Cyberduck rejects that invalid date and omits the file from directory listing.
I tried to use other kind of ftp clients with the server and found that they convert the invalid date of[[br]]
"02/29/2007" into "03/01/2007". I do not feel date conversion like that is good solution.[[br]]
However, it is also not good that Cyberduck silently ignores a file with invalid date.
Do you have any good idea?
The text was updated successfully, but these errors were encountered:
Currently when parsing a timestamp fails, the file is omitted in the directory listing. Because the timestamp is not valid I would argue it is the server software to fix here. If the file was created on a non-existant date the file should not even exist, does it?
Recently I noticed that Cyberduck does not list specific files on my home ftp server.[[br]]
I found that every file which is not listed has the date of "02/29/2004" as its timestamp.
Ordinary ftp servers (including ftpd of Mac OS X) return timestamp in a result of ls command, like:[[br]]
"-rw------- 1 masui masui 3147470848 Feb 29 2004 afo.mpg"
However, some ftp servers do not show year part of timestamp in directory listings, like:[[br]]
"-rwxr--r-- 1 owner 2487305280 Feb 29 12:00 bfo.mpg"
My home ftp server software is latter one. Is that a defect of the software?
When a file which has timestamp of "02/29/2004 12:00" (see "bfo.mpg" above) exists on the server,[[br]]
Cyberduck treats that information as "02/29/2007 12:00" because the server does not report year part[[br]]
of the timestamp. I think Cyberduck rejects that invalid date and omits the file from directory listing.
I tried to use other kind of ftp clients with the server and found that they convert the invalid date of[[br]]
"02/29/2007" into "03/01/2007". I do not feel date conversion like that is good solution.[[br]]
However, it is also not good that Cyberduck silently ignores a file with invalid date.
Do you have any good idea?
The text was updated successfully, but these errors were encountered: