Directory listing using a file mask/wildcards does not work anymore.

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
IK13
504 Command not implemented
Posts: 9
Joined: 2007-01-20 01:34

Directory listing using a file mask/wildcards does not work anymore.

#1 Post by IK13 » 2021-09-21 00:55

Last time I filed a bug I think was 15 years ago. I guess I might be one of the first users...

Anyways.

It seems that directory listing with a file mask (for example - NLST *.*) does not work anymore. Definitely used to work years ago.

User avatar
boco
Contributor
Posts: 26899
Joined: 2006-05-01 03:28
Location: Germany

Re: Directory listing using a file mask/wildcards does not work anymore.

#2 Post by boco » 2021-09-21 01:07

Seems there is no wildcard support in the new server.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Please do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

User avatar
botg
Site Admin
Posts: 35491
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Directory listing using a file mask/wildcards does not work anymore.

#3 Post by botg » 2021-09-21 07:39

The RFC does not specify how globbing is done, which makes it functionality one cannot rely on. It's an artifact of the time when humans were still punching in raw FTP commands, reading raw directory listings and client computers did not have the processing power to filter directory listings and not networking bandwidth to receive unfiltered listings.

Ever since, any client that wants to filter listings while being compatible with all types of servers need to do this filtering client-side. It's trivially easy for modern computers.

IK13
504 Command not implemented
Posts: 9
Joined: 2007-01-20 01:34

Re: Directory listing using a file mask/wildcards does not work anymore.

#4 Post by IK13 » 2021-09-21 16:21

Be as it may, it used to work in FZ. There likely is plenty of existing automation that relies on this. What's the benefit of removing it?
Filtering on the server will still be more efficient, regardless of client's resources and network bandwidth.
We have clients using different FTP servers and so far FZ is the only one that does not support wildcards that we have reports of. In fact, the one client that brought this to our attention is preparing to move away from FZ because they are caught between their existing version having another issue and the new version not supporting wildcards anymore.

User avatar
botg
Site Admin
Posts: 35491
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Directory listing using a file mask/wildcards does not work anymore.

#5 Post by botg » 2021-09-21 16:27

Why can't they fix the client software to not rely on unspecified behavior?

IK13
504 Command not implemented
Posts: 9
Joined: 2007-01-20 01:34

Re: Directory listing using a file mask/wildcards does not work anymore.

#6 Post by IK13 » 2021-09-21 16:46

botg wrote:
2021-09-21 16:27
Why can't they fix the client software to not rely on unspecified behavior?
They have no control over the client software. They can control the server, because it's theirs. The client software used for automation by connecting entities is not.

paupau
500 Command not understood
Posts: 1
Joined: 2021-09-23 14:45

Re: Directory listing using a file mask/wildcards does not work anymore.

#7 Post by paupau » 2021-09-23 15:12

botg wrote:
2021-09-21 07:39
The RFC does not specify how globbing is done, which makes it functionality one cannot rely on. It's an artifact of the time when humans were still punching in raw FTP commands, reading raw directory listings and client computers did not have the processing power to filter directory listings and not networking bandwidth to receive unfiltered listings.

Ever since, any client that wants to filter listings while being compatible with all types of servers need to do this filtering client-side. It's trivially easy for modern computers.
Fair enough, it's not mentioned in RFC 959. But it is a useful and often used feature. I wonder if there is any reason for changing the behaviour. Please consider adding tis functionality again.
"It's an artifact of the time when..." is in my opinion not a valid argument. A lot of modern APIs have possibilities to query and filter. Filtering on the client side may be VERY inefficient in some cases.

Post Reply