cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko (JIRA)" <>
Subject [jira] Closed: (COCOON-1049) encoding in Content-Type header is not set by serializers
Date Mon, 02 Oct 2006 17:24:22 GMT
     [ ]

Vadim Gritsenko closed COCOON-1049.

    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.10-dev (current SVN)
       Resolution: Fixed

RFC calls this value "media type". Added comments to getMimeType.

> encoding in Content-Type header is not set by serializers
> ---------------------------------------------------------
>                 Key: COCOON-1049
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.4
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Stefan Burkard
>         Assigned To: Cocoon Developers Team
>            Priority: Critical
>             Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
>         Attachments: MimeType.patch.txt
> The Cocoon Serializer does not set the encoding in the HTTP-Header, it just sets
> the mime-type in the header. additionally, it writes a meta-tag with mime-type
> and encoding in the html. 
> if now any component (for example apache webserver) sets a (wrong) default
> encoding in the header, most browsers use this header-encoding and ignore the
> meta-tag-encoding. 
> --------------------------------------
> here is an answer from jan uyttenhove from the cocoon-users-group to my question
> regarding this issue. i think this could help the developer:
> ATM, Cocoon set the meta content-type tag with the mime-type and the encoding of
> the serializer. Furthermore, response.setContentType *is* called, which is one
> of the ways to set the http encoding header. But it is called with argument
> mime-type only, e.g. response.setContentType("text/html"), and we should be able
> to do response.setContentType("text/html; charset=utf-8").
> We should be able to set the full content-type (with charset) in HttpEnvironment
> or in AbstractProcessingPipeline. I guess that involves changing at least the
> setSerializer(...) in AbstractProcessingPipeline and passing the encoding.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message