cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26997] - Encoding in HTTP-Header is not set by Serializer
Date Tue, 16 Mar 2004 17:38:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=26997>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=26997

Encoding in HTTP-Header is not set by Serializer

joerg.heinicke@gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Major                       |Critical
             Status|NEW                         |ASSIGNED



------- Additional Comments From joerg.heinicke@gmx.de  2004-03-16 17:38 -------
Severity changed to critical as it is no longer possible to use a different
encoding than the default one with a component (e.g. tomcat 4.1.29 and up) that
resets the content type from just mime type to mimetype + default encoding.

What's the correct place to fix this? I tested it via remote debugging at
HttpEnvironment.setContentType(String contentType) by resetting the contentType
myself from "text/html" to "text/html;charset=utf-8" and it works. But I guess
from here there is no access to the charset that should be set. Also the
AbstractProcessingPipeline has no access to encoding of the serializer. Must the
Serializer interface be extended (either by getEncoding() or by getContentType()
and the latter one instead of getMimeType())?

Mime
View raw message