452339 - FTP client of Firefox 3 has problems with native charakters (UTF8)

Status: RESOLVED DUPLICATE of bug 427089

(Firefox :: File Handling, defect)

Description

[kolAflash]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.1) Gecko/2008070400 SUSE/3.0.1-4.1 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.1) Gecko/2008070400 SUSE/3.0.1-4.1 Firefox/3.0.1

The ftp client of Firefox 3 can't download files which names contain native charakters like ßöäü

In Firefox 2 the problem doesn't seem to exist!

I testet the following:

Firefox 2 on MacOS 10.5 - all OK
Iceweasel 2 on Debian - all OK
Firefox 3 on openSUSE - didn't worked, couldn't download files with native letters
Firefox 3 on Windows - didn't worked...

The error Message in german is "Der Download kann nicht gespeichert werden, weil ein unbekannter Fehler aufgetreten ist. Bitte versuchen Sie es nochmals."

Tell me if you need more informations.

Reproducible: Always

Steps to Reproduce:
1. Get to an ftp-server and download a file which name contains native charakters like äüöß
Actual Results:  
Can't download the file.
German Error: "Der Download kann nicht gespeichert werden, weil ein unbekannter Fehler aufgetreten ist. Bitte versuchen Sie es nochmals."

Comment 1

[Cyrill]

Can confirm this bug. More than that, FireFox 3.x also cannot open directories, containing in their names native characters, generating "550 cwd failed  "/............." no such file or directory" message.
 Tested on multiple Windows systems, couple Linux (Mandriva 2008) and several MacOSx machines.
Opera, IE, Firefox 2.x.x line works fine.

In my case native characters are cyrillic, FTP-servers are Gene6 FTP and Serv-U.

Comment 2

[matmaul2003]

same here, seems like firefox doesn't detect utf-8 on ftp.
if I am in a folder, I see files with weird characters and I can't download them, it fails with this error : "550 CWD failed. "/Logiciels/aée.exe": directory not found".
if I change the encodage charset manually to utf-8, it works like a charm, no more weird characters and I can download the files !

so the missing part seems to be the utf-8 auto detection.

It works great with filezilla, so that's not my server fault.

Comment 3

[Bjarne (:bjarne)]

Can confirm this as well. Requesting it fixed for 3.1

Comment 4

[Bjarne (:bjarne)]

It looks like the "content-type" meta-tag specifies the charset as sent by the server, but the content is always converted to UTF-8. If the charset is retrieved from the server and specified on the page, I guess UTF-8 conversion should not happen.

Comment 5

[Bjarne (:bjarne)]

In my latest build from trunk I'm able to click on a file/dir even though the characters aren't displayed properly.

Comment 6

[Alexander L. Slovesnik]

Looks like duplicate of Bug 427089.