Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 16 Mar 2004 18:36:47 -0000
Message-ID: <20040316183647.14390.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 26997]  -
    Encoding in HTTP-Header is not set by Serializer

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


------- Additional Comments From m_rolappe@web.de  2004-03-16 18:36 -------
I think the correct place would Serializer. it has getMimeType() which is used
as callback to set the content type on the response. but I'm not sure whether
'mime type' is semantically equivalent to 'content type', which I'd assume
though. Serializer's (SitemapOutputComponent's) doc for getMimeType() doesn't
elaborate on that.

anyway, IMO serializers should remain passive, i.e. be asked for the content
type (including charset, since it depends on the serializer) by e.g.
AbstractProcessingPipeline.setupPipeline() which is to set the content type on
the Environment.