Custom Query (8117 matches)
Results (52 - 54 of 8117)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #886 | wilcard file listing on aliased directories | |||
| Description |
wildcard file listing does not appear to work correctly fir aliased directories. As an example, a directory 'common' is aliased as a link in the user's home directory :- <><> 230 Logged on ftp> dir 200 Port command successful 150 Opening data channel for directory list. drwxr-xr-x 1 ftp ftp 0 May 23 13:41 common -rw-r--r-- 1 ftp ftp 335 May 23 13:41 file1.txt -rw-r--r-- 1 ftp ftp 382 May 23 13:41 file2.txt -rw-r--r-- 1 ftp ftp 429 May 23 13:41 file3.txt 226 Transfer OK ftp: 237 bytes received in 0.01Seconds 23.70Kbytes/sec. ftp> dir f* 200 Port command successful 150 Opening data channel for directory list. -rw-r--r-- 1 ftp ftp 335 May 23 13:41 file1.txt -rw-r--r-- 1 ftp ftp 382 May 23 13:41 file2.txt -rw-r--r-- 1 ftp ftp 429 May 23 13:41 file3.txt 226 Transfer OK ftp: 180 bytes received in 0.01Seconds 18.00Kbytes/sec. ftp> cd common 250 CWD successful. "/common" is current directory. ftp> dir 200 Port command successful 150 Opening data channel for directory list. -r--r--r-- 1 ftp ftp 337 May 23 13:41 file1.txt -r--r--r-- 1 ftp ftp 384 May 23 13:41 file2.txt -r--r--r-- 1 ftp ftp 431 May 23 13:41 file3.txt 226 Transfer OK ftp: 180 bytes received in 0.01Seconds 18.00Kbytes/sec. ftp> dir f* 200 Port command successful 150 Opening data channel for directory list. 226 Transfer OK ftp> quit 221 Goodbye <><> Trying to do a "dir f*" in the user's home directory works ok but it fails in the "common" directory, which has been aliased. server version 0.98a server is accessible via the internet - I can provide logon credentials for you to verify setup if needed. |
|||
| #2146 | who's the owner/group of a file? | |||
| Description |
change its permissions. And the group would de nice too. Bye. |
|||
| #7804 | fixed | whitespace in filename cause download failure | ||
| Description |
I happen to have a file named ' 01.xxx.mp3' (xxx was Taiwanese). The whitespace prefixing the file name causes downloading errors. The filezilla server log shows the process. (000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> 227 Entering Passive Mode (140,113,205,141,8,75) (000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> RETR 01.xxx.mp3 (000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> 550 File not found Yes, the filezilla client correctly requested the filename as 'RETR 01.xxx.mp3', which has two whitespaces after RETR. It's just the server cannot find it. The issue can be worked around by deleting the prefixing whitespace. It's weird that when I tried to rename ' 01.xxx.mp3' to '01.xxx.mp3', windows 7 told me a file with that name already exists. I copied that file to the same directory, getting both '01.xxx.mp3' and ' 01.xxx.mp3'. Then, I deleted ' 01.xxx.mp3' and this time I can download '01.xxx.mp3' as usual. So I'm unsure if this issue belongs to filezilla server or windows 7 or the FTP protocol. Perhaps the problem is that all whitespaces between RETR and the filename are ignored by filezilla server? |
|||
