Custom Query (8143 matches)
Results (253 - 255 of 8143)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3984 | rejected | FileZilla show incorrect Date/Time on transfer | ||
| Description |
When I upload files, the server showed incorrect date/time |
|||
| #10038 | rejected | Unable to log in after update | ||
| Description |
I updated FileZilla when prompted today but receive an error message |
|||
| #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? |
|||
