glassfish reports setting character encoding too late in the request response
cycle
-----------------------------------------------------------------------------------
Key: JSPWIKI-320
URL: https://issues.apache.org/jira/browse/JSPWIKI-320
Project: JSPWiki
Issue Type: Bug
Components: Servlet Container/Java compatibility
Affects Versions: 2.6.2
Environment: glassfish, fedora, sun jre 1.6
Reporter: Clay Atkins
Priority: Minor
See this error in glassfish logs for nearly every request:
[#|2008-07-27T11:33:01.687-0500|WARNING|sun-appserver9.1|org.apache.coyote.tomca
t5.CoyoteRequest|_ThreadID=31;_ThreadName=httpSSLWorkerThread-443-6;_RequestID=f
e1c5e05-09e8-4b21-a9eb-c9eebc59c689;|PWC4011: Unable to set request character en
coding to UTF-8 from context /ewiki, because request parameters have already bee
n read, or ServletRequest.getReader() has already been called|#]
You have to set the character encoding before manipulating output.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.