Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of 1983-01-06@gmx.net designates
 212.227.17.22 as permitted sender)
MIME-Version: 1.0
Message-ID: 
 <trinity-b9d60622-3304-4e23-910a-4289c5a27894-1368604016221@3capp-gmx-bs18>
From: Michael-O <1983-01-06@gmx.net>
To: users@tomcat.apache.org
Subject: ErrorReportValve's char encoding ignored
Content-Type: text/plain; charset=UTF-8
Date: Wed, 15 May 2013 09:46:56 +0200 (CEST)
Importance: normal
Sensitivity: Normal

Hi folks,

I have modified the ErrorReportValve's messages outside of the one-byte range and the output got mangled. The response does not contain a char encoding anymore.

I know that the error valve does this:

response.setContentType("text/html");
response.setCharacterEncoding("utf-8");

but the setCharEnc method is completely ignored. Because the var usingWriter is already set to true. This happens in the ApplicationDispatcher#doForward line 393/394 when a servlet performs a forward.

Though a response.getReporter() is used but this one is completely unaware of the char encoding.

I am on Tomcat 6.0.35.

I presume this to be a bug. Should I file a BZ issue?

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org