#13174 closed Feature request (rejected)
Although it is not in the specification, accept LIST *.* (and LIST -a) as an option
| Reported by: | Rolland | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Server |
| Keywords: | LIST | Cc: | Rolland |
| Component version: | Operating system type: | ||
| Operating system version: |
Description
Hi,
My ftp client is an industrial plastic injection press using an old standard protocole called EuropMap63 that unfortunately uses "LIST *.*". I have no hope to the see protocole and the zillion of machines updated.
I have read the FAQ, forum's discussions, and past tickets : this is not a new subject. I understand your point about specifications.
So far my options are : use the 0.9.6 release (not a good idea) or use another server (would make me sad).
I just wonder how complex it would be to add an option like "accept non standard LIST commands" or equivalent. This would make it clear that this is no good ftp, but could allow many of us facing the same issue to keep using Filezilla. The option could for example treat all "LIST whatever" calls as "LIST" even for files & directories.
Change History (2)
comment:1 by , 4 weeks ago
| Resolution: | → rejected |
|---|---|
| Status: | new → closed |
comment:2 by , 4 weeks ago
Any filtering needs to be done client-side.
Even if there were server-side filtering, the client still has to filter the results again, as clients should not blindly trust remote servers.
No, this creates an ambiguity, one would no longer be able to list the specific file that contain asterisks in the name, or the directory literally named "-a".