LIST and NLST don't support the ? wildcard

[earlsoft]

The LIST and NLST don't support using ? as a wildcard.
RFC 959 says:
The pathname should specify a directory or other system-specific file group descriptor.

Id have thoguht these would be passed straight to windows to filter the matches.

The logs are as follows:

ftp> dir ??????.jpg
200 Port command successful
550 Directory not found.

ftp> dir latest.jpg
200 Port command successful
150 Opening data channel for directory list.
-rw-r--r-- 1 ftp ftp 8748 May 14 14:35 latest.jpg
226 Transfer OK
ftp: 61 bytes received in 0.00Seconds 61000.00Kbytes/sec.

ftp> dir lates?.jpg
200 Port command successful
550 Directory not found.

The logs from FileZilla server itself are:
(000037) 14/05/2008 14:42:04 - sentry (127.0.0.1)> LIST ??????.jpg
(000037) 14/05/2008 14:42:04 - sentry (127.0.0.1)> 550 Directory not found.
(000037) 14/05/2008 14:42:10 - sentry (127.0.0.1)> PORT 127,0,0,1,18,190
(000037) 14/05/2008 14:42:10 - sentry (127.0.0.1)> 200 Port command successful
(000037) 14/05/2008 14:42:10 - sentry (127.0.0.1)> LIST latest.jpg
(000037) 14/05/2008 14:42:10 - sentry (127.0.0.1)> 150 Opening data channel for directory list.
(000037) 14/05/2008 14:42:10 - sentry (127.0.0.1)> 226 Transfer OK
(000037) 14/05/2008 14:42:13 - sentry (127.0.0.1)> PORT 127,0,0,1,18,191
(000037) 14/05/2008 14:42:13 - sentry (127.0.0.1)> 200 Port command successful
(000037) 14/05/2008 14:42:13 - sentry (127.0.0.1)> LIST lates?.jpg
(000037) 14/05/2008 14:42:13 - sentry (127.0.0.1)> 550 Directory not found.

All 3 of the requests listed above should have returned the same single match each time.

[Tim Kosse]

Not a bug. The FTP specifications don't mention wildcard support at all.

[earlsoft]

No, it does say "system-specific file group descriptor."
On windows, this is * and ? as wildcard characters.

AFAIK, every other server handles this as expected so while you may not think it is a bug, it is contrary to the general expectation. (That sounded too much liek sales speak :|