Opened 19 years ago
Last modified 17 years ago
#2449 closed Feature request
Windows safe filenames
| Reported by: | whangiorva | Owned by: | Alexander Schuch |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Cc: | whangiorva, Alexander Schuch | |
| Component version: | Operating system type: | ||
| Operating system version: |
Description
A lot of times when I use filezilla to download some
stuff, it'll get confused by the unix / linux
filenames.
As a result, it'll get confused by the directory names
and try to overwrite stuff it just downloaded. Either
from the same directory (similar filename) or from
another directory that has similar contents (but
perhaps a different version.)
Or worse, it'll create the directory or file, but it
wont be accessible under windows. Things like NUL,
CON, etc. Those and more are reserved under Windows.
They date back to DOS, but are still a problem in
windows.
Perhaps Filezilla should have an option (enabled by
default) to create Windows safe filenames.
Note:
See TracTickets
for help on using tickets.
Windows should not allow any application to create invalid file or directory names. So if FileZilla can successfully create a file or directory with a reserved name instead of getting an error, Windows is to blame.
However, I agree that invalid characters should be filtered somehow, like for example colons (:) or backslashes (\).
Anyway, this is a known bug in FileZilla 3, so please check the following FileZilla 3 bug report for further details:
[ 1792985 ] Filter invalid characters from filename
Closing this RFE.