Opened 10 years ago

Last modified 7 years ago

#4791 new Bug report

FileZilla can't handle long path names

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

Description

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:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp

There is also a discussion on this forum page:

http://forum.sysinternals.com/printer_friendly_posts.asp?TID=5676

Change History (2)

comment:1 Changed 10 years ago by Tim Kosse

UNC stands for Uniform Naming Convention, not unicode.

comment:2 Changed 7 years ago by Igor

Cc: i3v@… added

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

Note: See TracTickets for help on using tickets.