Re: Firefox sets wrong encoding to directory listings?

[Martin Sourada]

On Sun, 2007-11-25 at 18:56 +0100, nodata wrote:
>  What character set does your filesystem use?
>   
Should be UTF-8. It's ext3 on LVM with no special settings.

>  What does Apache display if you create a file with a Japanese
> filename?
>  Copy and paste from yahoo.jp to test.
>   
No need to copy and paste, I use scim for Japanese input ;-)

I created a file named "風" [kaze; wind]. When I try to access it with
firefox via vsftpd it has both wrong encoding and is inaccessible (the
link is both wrongly displayed and wrongly used, but when I manually 
write the character into location bar the file can be opened), when I 
access it with firefox via httpd (Apache) it is only wrongly displayed 
but works ok. If I manually set the encoding in firefox to UTF-8 the 
name is fixed both when accessed via vsftpd (which fixes the link as 
well) and via httpd. Just in case you are interested, the wrong string 
looks like "風".

Looks like both vsftpd and httpd (Apache) are not very UTF-8 friendly :-(

Thanks,
Martin

Firefox sets wrong encoding to directory listings?

[Ralf Ertzinger]

Hi.

On Sun, 25 Nov 2007 23:09:00 +0100 (CET), Martin Sourada wrote:

>  Looks like both vsftpd and httpd (Apache) are not very UTF-8
>  friendly :-( 
httpd and vsftpd do not care about UTF-8 when displaying files,
they just read the filename from the disk and push it to the
client. It's up to the client to interpret the data.
HTTP has the ability to send a charset with the data, while FTP
has not.

Using "HEAD <yoururl>" you can easily inspect the header information
sent by your HTTP server and look if it sets the charset information
correnctly. HEAD is part of the perl-libwww-perl package.

Firefox sets wrong encoding to directory listings?

[Martin Sourada]

On Mon, 2007-11-26 at 09:47 +0100, Ralf Ertzinger wrote:
>  Hi.
>  
>  On Sun, 25 Nov 2007 23:09:00 +0100 (CET), Martin Sourada wrote:
>  
>  > Looks like both vsftpd and httpd (Apache) are not very UTF-8
>  > friendly :-(
>  
>  httpd and vsftpd do not care about UTF-8 when displaying files,
>  they just read the filename from the disk and push it to the
>  client. It's up to the client to interpret the data.
>  HTTP has the ability to send a charset with the data, while FTP
>  has not.
>   
Didn't know that. Then I wonder, why clients defaults to ISO-8859-1,
while most of the today's filesystems use UTF-8...

>  Using "HEAD <yoururl>" you can easily inspect the
> header information
>  sent by your HTTP server and look if it sets the charset information
>  correnctly. HEAD is part of the perl-libwww-perl package.
>   
Thanks. The result is not what I'd like.


HEAD 127.0.0.1
200 OK
Connection: close
Date: Mon, 26 Nov 2007 09:52:12 GMT
Accept-Ranges: bytes
Server: Apache/2.2.6 (Fedora)
Content-Type: text/html; charset=UTF-8
Client-Date: Mon, 26 Nov 2007 09:52:12 GMT
Client-Peer: 127.0.0.1:80
Client-Response-Num: 1

HEAD 127.0.0.1/ftp/pub
200 OK
Connection: close
Date: Mon, 26 Nov 2007 09:52:04 GMT
Server: Apache/2.2.6 (Fedora)
Content-Type: text/html;charset=ISO-8859-1
Client-Date: Mon, 26 Nov 2007 09:52:04 GMT
Client-Peer: 127.0.0.1:80
Client-Response-Num: 1

In root there is index.xhtml which is normally displayed by default,
in /ftp/pub there is no html file, only folders, so normally it is
displayed as folder listing.

Thanks,
Martin

Firefox sets wrong encoding to directory listings?

[Benny Amorsen]

> >>>> "MS" == Martin Sourada
> <martin.sourada(a)seznam.cz&gt; writes: 
MS> Didn't know that. Then I wonder, why clients defaults to
MS> ISO-8859-1, while most of the today's filesystems use UTF-8...

HTTP clients generally do as they are told (except for IE, but that's
another rant). Apache tells them ISO-8859-1 in your case, so that's
what they display.

Have you tried IndexOptions Charset=UTF-8?


/Benny

Firefox sets wrong encoding to directory listings?

[Christopher Aillon]

On 11/26/2007 10:56 AM, Martin Sourada wrote:
>  HEAD 127.0.0.1
>  200 OK
>  Connection: close
>  Date: Mon, 26 Nov 2007 09:52:12 GMT
>  Accept-Ranges: bytes
>  Server: Apache/2.2.6 (Fedora)
>  Content-Type: text/html; charset=UTF-8
>  Client-Date: Mon, 26 Nov 2007 09:52:12 GMT
>  Client-Peer: 127.0.0.1:80
>  Client-Response-Num: 1
>  
>  HEAD 127.0.0.1/ftp/pub
>  200 OK
>  Connection: close
>  Date: Mon, 26 Nov 2007 09:52:04 GMT
>  Server: Apache/2.2.6 (Fedora)
>  Content-Type: text/html;charset=ISO-8859-1 
                           ^^^^^^^^^^^^^^^^^^
There's your problem.  Get Apache to stop sending that, and send UTF-8 
there instead and you'll be fine.  This is a server configuration issue, 
not a Firefox issue.

>  Client-Date: Mon, 26 Nov 2007 09:52:04 GMT
>  Client-Peer: 127.0.0.1:80
>  Client-Response-Num: 1
>  
>  In root there is index.xhtml which is normally displayed by default,
>  in /ftp/pub there is no html file, only folders, so normally it is
>  displayed as folder listing.
>  
>  Thanks,
>  Martin
>

Firefox sets wrong encoding to directory listings?

[Martin Sourada]

On Mon, 2007-11-26 at 13:12 +0100, Benny Amorsen wrote:
>  >>>>> "MS" == Martin Sourada
> <martin.sourada(a)seznam.cz&gt; writes:
>  
>  MS> Didn't know that. Then I wonder, why clients defaults to
>  MS> ISO-8859-1, while most of the today's filesystems use UTF-8...
>  
>  HTTP clients generally do as they are told (except for IE, but that's
>  another rant). Apache tells them ISO-8859-1 in your case, so that's
>  what they display.
>   
Well, I was talking rather about ftp clients in this very paragraph.

>  Have you tried IndexOptions Charset=UTF-8?
>   
Thanks, that fixes the problem :)

>  
>  /Benny
>  
>   
Martin