[
https://issues.apache.org/jira/browse/AXIS2-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065439#comment-13065439
]
Vincent Tang commented on AXIS2-5057:
-------------------------------------
Hi, I'm the creator of the JIRA issues. I saw Andreas Veithen commented on
2/Jun/2011 that it will be fixed in version 1.5.5. But I don't see any work
history on the issue. Have we already identified that it's a bug ? and any work
on it? Thanks in advance if you have any update.
> Content-Type is not set MTOM format when the request has Accept-Encoding set
> with gzip
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-5057
> URL: https://issues.apache.org/jira/browse/AXIS2-5057
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, mtompolicy
> Affects Versions: 1.4.1, 1.5.4
> Environment: Windows 32
> Reporter: Vincent Tang
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
