Custom Query (8096 matches)
Results (130 - 132 of 8096)
|#882||unable to access directories with leading/trailing spaces|
It appears that if someone has created a directory on an ftp server with a leading or trailing space in the directory name (i.e. " directoryname" or "directoryname "), the FileZilla client (Windows, v2.2.13c) is unable to descend into that directory. I believe this to be an issue with the client rather than the server since I am unable to duplicate this issue with gftp under Linux or coreftp under Windows.
Logs on the server side look like FileZilla is stripping the leading / trailing spaces off the file names (directories in test below are named " leading space" and "trailing space ":
dsl-100.netexpress.net UNKNOWN nobody [18/May/2005:11:08:19 -0500] "USER shagz" 331 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:20 -0500] "PASS (hidden)" 230 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:20 -0500] "FEAT" 211 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:20 -0500] "SYST" 215 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:20 -0500] "PWD" 257 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:25 -0500] "CWD leading space" 550 - dsl-100.netexpress.net UNKNOWN shagz [18/May/2005:11:08:29 -0500] "CWD trailing space" 550 -
client -side logs are attached.
The server this was discovered with is a Linux machine running proftpd. I can provide test login credentials if needed.
|#890||Delete many files in directory takes a long time|
In a directory, deleting 500+ files takes a very long time.
Time between each file is longer with more files in queue. Deleting 2000 files may take 30 minutes and more.
|#891||long path names above 255 chars|
on the remote server i am unable to list a directory if the path is longer than 255 chars. Filezilla then simply trunk the path to 255 chars.
is it Filezilla or FTP, that i don't know.