[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rampart-dev
Subject:    [jira] [Created] (AXIS2-5057) Content-Type is not set MTOM format
From:       "Vincent Tang (JIRA)" <jira () apache ! org>
Date:       2011-05-31 17:18:47
Message-ID: 2100048605.56643.1306862327699.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]

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.5.4, 1.4.1
         Environment: Windows 32
            Reporter: Vincent Tang
             Fix For: 1.5.5


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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]