CXF not sending charset information on responses

Details

  • Type: Patch submission Patch submission
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.1.1
  • Fix Version/s: 3.0.1, 3.1.0
  • Component/s: Modules: CXF
  • Labels:
    None
  • Environment:

    Ubuntu 8.10 with sun-jdk 1.6.0_10

  • User impact:
    High
  • Similar Issues:
    None

Description

When running the echo example with cxf endpoint i get this response:
Transfer-Encoding chunked
Date Tue, 02 Dec 2008 04:52:33 CET
#status# HTTP/1.1 200 OK
Expires Tue, 02 Dec 2008 04:52:33 CET
Connection close
Content-Type text/xml
Server Mule Core/2.1.1

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:echoResponse xmlns:ns1="http://echo.example.mule.org/">
<text>per med æøå</text>
</ns1:echoResponse>
</soap:Body>
</soap:Envelope>

Which don't contain any information that its ecoded in UTF-8 so soapUI and .net clients assumes us-asci. Which is correct according to the SOAP standard.

request :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:echo="http://echo.example.mule.org/">
<soapenv:Header/>
<soapenv:Body>
<echo:echo>
<!-Optional:->
<text>per med æøå</text>
</echo:echo>
</soapenv:Body>
</soapenv:Envelope>

  1. File
    cxf-patch-20090717
    16/Jul/09 04:58 PM
    9 kB
    Yuji Yamano
  2. XML File
    echo-cxf-config.xml
    13/Feb/09 05:36 AM
    2 kB
    Idar Borlaug
  3. Java Source File
    FixCxfEncodingInterceptor.java
    26/Feb/09 08:52 AM
    1 kB
    Idar Borlaug
  4. Java Source File
    FixEncoding.java
    13/Feb/09 05:36 AM
    2 kB
    Idar Borlaug

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Idar Borlaug added a comment -

This also affects the xml syntax not just the content.

Show
Idar Borlaug added a comment - This also affects the xml syntax not just the content.
Hide
Permalink
Ove Gram Nipen added a comment -

This behaviour breaks web service clients written in .net, because they fail to interpret the response as being in utf-8 encoding. This is a show-stopper for us.

Show
Ove Gram Nipen added a comment - This behaviour breaks web service clients written in .net, because they fail to interpret the response as being in utf-8 encoding. This is a show-stopper for us.
Hide
Permalink
Idar Borlaug added a comment -

The FixEncoding.java file, fixes the xml encoding information.
See echo-cxf-config.xml for example config.

The HTTP header is still only reporting text/xml and not text/xml, Charset: utf-8

Show
Idar Borlaug added a comment - The FixEncoding.java file, fixes the xml encoding information. See echo-cxf-config.xml for example config. The HTTP header is still only reporting text/xml and not text/xml, Charset: utf-8
Hide
Permalink
D Henton added a comment -

I've got the same issue in trying to talk to an external .Net service. Like the man says, This is a show-stopper for us. We routinely send non ascii information.

Show
D Henton added a comment - I've got the same issue in trying to talk to an external .Net service. Like the man says, This is a show-stopper for us. We routinely send non ascii information.
Hide
Permalink
Idar Borlaug added a comment -

We got a CXFInterceptor that now addes the correct HTTP header. If one adds these two interceptors to the cxf bus, it will work.
Please add these or change the cxf bus in mule so we don't have to add these manually. This should be done in mule.

Show
Idar Borlaug added a comment - We got a CXFInterceptor that now addes the correct HTTP header. If one adds these two interceptors to the cxf bus, it will work. Please add these or change the cxf bus in mule so we don't have to add these manually. This should be done in mule.
Hide
Permalink
Dan Diephouse added a comment -

I agree that this is a critical bug. I'll see if I can get a fix in for our next release, but can you do me a favor and try this on 2.2 before I do? I think I may have fixed it already.

Show
Dan Diephouse added a comment - I agree that this is a critical bug. I'll see if I can get a fix in for our next release, but can you do me a favor and try this on 2.2 before I do? I think I may have fixed it already.
Hide
Permalink
S J added a comment -

I encountered this same issue in mule 2.2.1.

I was able to confirm this bug by inspecting the headers of the HTTP request message through tcpmon. The Content-type header is set to 'text/xml'.

Show
S J added a comment - I encountered this same issue in mule 2.2.1. I was able to confirm this bug by inspecting the headers of the HTTP request message through tcpmon. The Content-type header is set to 'text/xml'.
Hide
Permalink
Yuji Yamano added a comment -

Here is the patch for Mule 3.x branch. I hope it fixes the problem.

Please save test-data-messages_ja.src as UTF-8. It includes Japanese String.

Show
Yuji Yamano added a comment - Here is the patch for Mule 3.x branch. I hope it fixes the problem. Please save test-data-messages_ja.src as UTF-8. It includes Japanese String.
Hide
Permalink
david turpin added a comment -

Did anybody try this patch ?
And is it working only on a 3.x version or also on a 2.2.x version ?

Show
david turpin added a comment - Did anybody try this patch ? And is it working only on a 3.x version or also on a 2.2.x version ?
Hide
Permalink
P.Oikari pnirvinn added a comment -

Really annoying bug if other side is .NET

Fortunately FixCxfEncodingInterceptor.java works Ok on 2.2.1/2.2.2

Just wondering how this is still unfixed after almost 2 years...

Show
P.Oikari pnirvinn added a comment - Really annoying bug if other side is .NET Fortunately FixCxfEncodingInterceptor.java works Ok on 2.2.1/2.2.2 Just wondering how this is still unfixed after almost 2 years...
Hide
Permalink
Idar Borlaug added a comment -

That bugs like this isn't fixed is the reason we are facing out Mule in our application. We are using spring instead, much higher quality.

Show
Idar Borlaug added a comment - That bugs like this isn't fixed is the reason we are facing out Mule in our application. We are using spring instead, much higher quality.
Hide
Permalink
Ken Yagen added a comment -

Needs patch submitted state

Show
Ken Yagen added a comment - Needs patch submitted state
Hide
Permalink
Ken Yagen added a comment -

raising priority based on number of votes

Show
Ken Yagen added a comment - raising priority based on number of votes
Hide
Permalink
Mike Schilling added a comment -

The submitted patch was applied. (Other than the change to the CXF connector class, which no longer exists.)

Show
Mike Schilling added a comment - The submitted patch was applied. (Other than the change to the CXF connector class, which no longer exists.)

People

  • Assignee:
    Mike Schilling
    Reporter:
    Idar Borlaug
Vote (11)
Watch (9)

Dates

  • Created:
    Updated:
    Resolved: