Opened 16 years ago
Closed 16 years ago
#4420 closed Bug report (wontfix)
FileZilla can't acces Directory on Server
Reported by: | Kevin Gut | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Directory wrong list access | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | Windows XP |
Description
Hello, FileZilla Team
(I'm from Switzerland, so my english may be bad)
If I connect with FileZila to 213.251.167.117:21 (public server)
He gives me a List of four Directories, I can only access the Directory named "1" with clicking on it, my network capture toool told me, that the inaccessible Dirs contain some spaces at the Beginning or the end of the name (and one subdirectory is only named with a space, but by entering / / into the ), by entering the name manually I can access the Directory and the Files in it.
As an attachment, I give you the result from my network capturing tool, in the Window you can see the Hex and ASCII output, on the
Bottom, again, ASCII (but with line breaks like in Notepad)
Hope this Information helps to solve this issue
Attachments (1)
Change History (3)
by , 16 years ago
Attachment: | err_list.png added |
---|
comment:1 by , 16 years ago
Replying to ayra:
Two thins missing
-->I am Using Version 3.2.3.1
-->Filezilla lists the Directory with only a Space char as Name wrong, it displays the date and time of the Dir instead.
comment:2 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Using LIST, leading or trailing spaces are indistinguishable from padding characters.
Due to that reason, 3.2.4-rc1 and upwards use MLSD that supports leading and trailing whitespace.
Your server does not support MLSD though, you have to upgrade to a proper server or refrain from using filename with leading or trailing spaces.
Network Capture shows Directory List in HEX