[
https://issues.apache.org/jira/browse/CXF-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edwin updated CXF-8234:
-----------------------
Description:
We enabled the transformation feature based on
[https://cxf.apache.org/docs/transformationfeature.html], but then we noticed
that 'charset' is missing in response Content-Type. This is probably due to
"disable.outputstream.optimization" being set to true by
TransformOutInterceptor but the documentation states that
"disable.outputstream.optimization" needs to be set to true prior to CXF
versions 3.2.6 and 3.1.17.
We are using 3.2.6 and we even upgraded to 3.2.12 and the behavior is the same.
I also checked TransformOutInterceptor in master branch and it is still
setting "disable.outputstream.optimization" to true.
Is there a workaround for this issue in 3.2.x branch and can this be fixed in
future releases?
Here are part of the headers with transformation:
{code:java}
HTTP/1.1 200
Content-Type: text/xml
Transfer-Encoding: chunked
Date: Sun, 08 Mar 2020 22:41:04 GMT{code}
And here are part of the headers when transformation is not used:
{code:java}
HTTP/1.1 200
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Sun, 08 Mar 2020 22:40:43 GMT
{code}
was:
We enabled the transformation feature based on
[https://cxf.apache.org/docs/transformationfeature.html], but then we noticed
that 'charset' is missing in response Content-Type. This is probably due to
"disable.outputstream.optimization" being set to true by
TransformOutInterceptor but the documentation states that
"disable.outputstream.optimization" needs to be set to true prior to CXF
versions 3.2.6 and 3.1.17.
We are using 3.2.6 and we even upgraded to 3.2.12 and the behavior is the same.
I also checked TransformOutInterceptor in master branch and it is still
setting "disable.outputstream.optimization" to true.
Is there a workaround for this issue in 3.2.x branch and can this be fixed in
future releases?
Here are part of the headers with transformation:
{code:java}
// code placeholder
{code}
HTTP/1.1 200
Content-Type: text/xml
Transfer-Encoding: chunked
Date: Sun, 08 Mar 2020 22:30:41 GMT
> Response Content-Type is missing 'charset' when Transformation feature is
> enabled
> ---------------------------------------------------------------------------------
>
> Key: CXF-8234
> URL: https://issues.apache.org/jira/browse/CXF-8234
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 3.2.6, 3.2.12
> Reporter: Edwin
> Priority: Major
>
> We enabled the transformation feature based on
> [https://cxf.apache.org/docs/transformationfeature.html], but then we noticed
> that 'charset' is missing in response Content-Type. This is probably due to
> "disable.outputstream.optimization" being set to true by
> TransformOutInterceptor but the documentation states that
> "disable.outputstream.optimization" needs to be set to true prior to CXF
> versions 3.2.6 and 3.1.17.
> We are using 3.2.6 and we even upgraded to 3.2.12 and the behavior is the
> same. I also checked TransformOutInterceptor in master branch and it is
> still setting "disable.outputstream.optimization" to true.
> Is there a workaround for this issue in 3.2.x branch and can this be fixed in
> future releases?
>
> Here are part of the headers with transformation:
> {code:java}
> HTTP/1.1 200
> Content-Type: text/xml
> Transfer-Encoding: chunked
> Date: Sun, 08 Mar 2020 22:41:04 GMT{code}
>
> And here are part of the headers when transformation is not used:
>
> {code:java}
> HTTP/1.1 200
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Sun, 08 Mar 2020 22:40:43 GMT
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
