Is the same thing happening if you point your browser directly at the Tomcat
port instead of going to the Apache httpd?
--a.
----- Original Message -----
From: "tsarfion" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, October 15, 2006 11:56 AM
Subject: Content-Type in HTTP-Header is ISO-8859-1 instead of UTF-8
I'm using Roller 3.0 RC3. Some pages have the charset ISO-8859-1 instead
of
UTF-8 in the HTTP header. It is the case for all the pages with a *.do
path
in the URL at least.
Here is a response with a wrong charset:
HTTP/1.1 200 OK
Date: Sun, 15 Oct 2006 10:04:43 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) mod_jk/1.2.14 PHP/4.3.10-16
Content-Language: de-CH
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=ISO-8859-1
389a
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<title>Front Page: New Entry</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
...
When I edit a text with German umlauts it does not get stored correctly in
the database and does not display correctly. When I switch the encoding to
UTF-8 manually in my browser and save a message with umlauts, it is stored
and correctly. When a view the web log entry as a guest, the charset in
the
HTTP response is UTF-8.
The code in the JSPs and the configuration settings seem to set the
charset
correctly.
Thank you for your help.
tsarfion
--
View this message in context:
http://www.nabble.com/Content-Type-in-HTTP-Header-is-ISO-8859-1-instead-of-UTF-8-tf2448067s12275.html#a6823677
Sent from the Roller - User mailing list archive at Nabble.com.
