Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 66402 invoked by uid 500); 7 Jun 2003 21:36:56 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 66388 invoked from network); 7 Jun 2003 21:36:55 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 7 Jun 2003 21:36:55 -0000 Received: (qmail 21091 invoked by uid 50); 7 Jun 2003 21:39:15 -0000 Date: 7 Jun 2003 21:39:15 -0000 Message-ID: <20030607213915.21090.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: cocoon-dev@xml.apache.org Cc: Subject: DO NOT REPLY [Bug 14327] - [PATCH] JSPEngineImpl response charset should be specified with Content-Type. X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14327 [PATCH] JSPEngineImpl response charset should be specified with Content-Type. ------- Additional Comments From bruno@outerthought.org 2003-06-07 21:39 ------- I don't know much about this, but I think it depends on whether this thing is being used by the JSPGenerator or by the JSPReader. For the JSPReader, the behaviour from this patch seems more correct. The JSPGenerator on the other hand will parse the generated JSP output always as UTF-8, so it should also be serialized as UTF-8. Maybe the JSPGenerator should be changed to determine the encoding in the same way as the JSPEngineImpl does?