Opened 15 years ago

Closed 9 years ago

Last modified 9 years ago

#4792 closed Bug report (rejected)

FileZilla can't handle long path names

Reported by: njyoder Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc: i3v@…
Component version: Operating system type: Windows
Operating system version:


Because you can't create a single ticket for both FileZilla client and server, I have created a duplicate one for each.

Both FileZilla client & server can't handle long path names. They are programmed to use the MAX_PATH constant when dealing with files, which only allows a full path/filename of up to 260 characters. This is only a limitation of FAT32 and doesn't exist on NTFS. This results in errors making it impossible to transfer files whose path names are too long.

For NTFS, there are ways of working around this limitation, allowing for path names of 32,768 characters (specified by GetVolumeInformation (lpMaximumComponentLength)). Utilizing UNC (unicode) filenames allows you to get around this.

For reference, see this MSDN page:

There is also a discussion on this forum page:

Change History (3)

comment:1 by Igor, 11 years ago

Cc: i3v@… added

I've just added a related (as I believe) bug here.

comment:2 by Tim Kosse, 9 years ago

Resolution: rejected
Status: newclosed

Using UNC paths is dangerous. It disables syntax checking and allows creating files and directories that are inaccessible in most programs, including Explorer.

As long the native Windows tools cannot handle long paths, no such support will be implemented in FileZilla Server either.

comment:3 by Igor, 9 years ago

That's a pity (that this ticket got closed)...

AFAIK, there's no other simple mechanism for accessing these files. In many cases users do need long paths. A number of related bugs (see references in the ticket, referenced in my comment above)

I'm not sure how exactly it could be dangerous... IMHO, most file browsers do support UNC, including windows explorer (its UNC support is being improved gradually, as far as I've noticed).

Note: See TracTickets for help on using tickets.