Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leap year and a server which does not show year part of timestamp #1205

Closed
cyberduck opened this issue Aug 4, 2007 · 1 comment
Closed
Assignees
Labels
bug ftp FTP Protocol Implementation wontfix

Comments

@cyberduck
Copy link
Collaborator

35f422c created the issue

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?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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?

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug ftp FTP Protocol Implementation wontfix
Projects
None yet
Development

No branches or pull requests

2 participants