[
https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766058#action_12766058
]
Daniel Kulp commented on CXF-2475:
----------------------------------
This is working exactly as it's supposed to and this patch completely breaks
things all over the place.
By default, nothing sets the the character encoding on the response. Thus,
normally, whenever you call getCharacterEncoding(), it will return "ISO-8859-1"
which is the default. This breaks all kinds of things that try to send
strings and such outside the ISO-8859-1 character space.
According to the specs and WSI-BP, the current behavior is correct. We should
be responding with the character set as what the client sent the incoming
message with. If the client sent in UTF-8, we respond with UTF-8. If they
send with UTF-16, we respond in kind.
Anyway, what is the use case that makes you think this is a bug that needs
fixing?
> When writing XML response, CXF uses request encoding instead of response
> encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding
> instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
