Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#5210 closed Bug report (rejected)

FileZilla ignores leading space of filename

Reported by: Rich Rarey Owned by:
Priority: normal Component: FileZilla Client
Keywords: leading space in filename Cc:
Component version: Operating system type: Windows
Operating system version: WINXP SP3

Description

version 3.3.2
CONDITIONS:

  1. A server has a file with a leading space in its filename.
  2. FileZilla's directory display parses the name, removes the leading space, and displays the filename without the leading space.
  3. FileZilla is then unable to correctly reference the file by name for file deletion, renaming, etc. as the leading space is "missing" from commands issued by FileZilla.

I have confirmed this behavior by deliberately creating a file with a leading space on my server, and observing FileZilla's behavior, and noting FileZilla's attempts in the server's xferlog.

A bug search showed obscure reports made about this three years ago, but not well described.

Change History (3)

comment:1 by Tim Kosse, 10 years ago

Resolution: rejected
Status: newclosed

This happens on FTP servers not supporting the MLSD command. On those servers FileZilla falls back to LIST. Unfortunately the listing format returned by LIST is not standardized. It is impossible to distinguish leading spaces from padding.

To solve this issue, simply upgrade to a modern server supporting the MLSD command o refrain from using leading spaces.

comment:2 by Alexander Schuch, 8 years ago

The issue was "re-opened" as #8326.

in reply to:  description comment:3 by Peter Zelchenko, 7 years ago

Replying to rrarey:

version 3.3.2
CONDITIONS:

  1. A server has a file with a leading space in its filename.
  2. FileZilla's directory display parses the name, removes the leading space, and displays the filename without the leading space.
  3. FileZilla is then unable to correctly reference the file by name for file deletion, renaming, etc. as the leading space is "missing" from commands issued by FileZilla.

I have confirmed this behavior by deliberately creating a file with a leading space on my server, and observing FileZilla's behavior, and noting FileZilla's attempts in the server's xferlog.

A bug search showed obscure reports made about this three years ago, but not well described.

Temporary workaround if you need to get to your files:

In the "Remote site:" field, type the directory exactly, including any leading spaces:

/Volumes/SAN/Data/Users/john/ My stuff
(note leading space above)

This will take you to the directory. You can also use psftp (from PuTTY) to modify the directory names permanently.

Note: See TracTickets for help on using tickets.