Opened 15 years ago

Closed 12 years ago

#4841 closed Bug report (worksforme)

Wrong routing when downloading some exoticly named files

Reported by: tropicalm Owned by:
Priority: low Component: FileZilla Client
Keywords: wrong routing Cc:
Component version: Operating system type: Windows
Operating system version: Vista

Description

I had an occasion where the remote filename was .\www\automate\LISTE.csv, and it created a local folder ./www/automate/LISTE.csv to accomodate it...

I agree that Windows wouldn't like to welcome this file as is, with that filename that is, but putting it into another folder is worse. Maybe a middle solution could be negotiated? Like replacing unauthorised characters with '_' or ?

Attachments (1)

filename_wrong_routing.jpg​ (151.8 KB ) - added by tropicalm 15 years ago.
An actual exemple of wrong local routing

Download all attachments as: .zip

Change History (3)

by tropicalm, 15 years ago

Attachment: filename_wrong_routing.jpg​ added

An actual exemple of wrong local routing

comment:1 by Tim Kosse, 15 years ago

Status: new → moreinfo

Which version of FileZilla are you using?

comment:2 by Alexander Schuch, 12 years ago

Resolution: → worksforme
Status: moreinfo → closed

I tested this using FileZilla 3.5.3 on Windows Server 2003 Enterprise Edition.

Subdirectories are created when "Filter invalid characters in filenames" is disabled in the transfer settings. When enabled, the backslash is properly replaced by the given character.

Note: See TracTickets for help on using tickets.