[AXIS2-5057] Content-Type is not set MTOM format when the request has Accept-Encoding set with gzip

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.1, 1.5.4
• Component/s: jaxws, mtompolicy
• Environment: Windows 32
• Assignee: Unassigned
• Reporter: Vincent Tang
• Created: 31/May/11 17:18
• Updated: 14/Jul/11 18:25

Description

I don't if it's a bug or a setting that I can set and make it work.

I have a JAX-WS web services application with MTOM enabled using Axis2 v1.4.1. When I set Accept-Encoding to gzip in the request, the response body is encoded but the Content-Type HTTP header is text/xml. It causes my client (also Axis2 1.4.1) can not understand the response and failed. When the client app sents a request and our JAX-WS services has an error. Axis2 sends a SOAP fault back to the client, at this time, the HTTP body is encoded and HTTP header Content-Type is set to the correct MTOM format.

Without Accept-Encoding:gzip in the request, Axis2 can respond correctly with MTOM Content-Type header.

I see the same issue in Axis2 V1.5.4 too.