[ 
https://issues.apache.org/jira/browse/CXF-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505946
 ] 

Steven E. Harris commented on CXF-687:
--------------------------------------

I'm seeing this emanating from a CXF client built against the CXF 
2.0-incubator-SNAPSHOT version, looking at what's captured in TCPMon.

My client is configured via a jaxws:client element, adding an 
"addressingPolicy" feature. Elsewhere in the same XML file, I have an 
http:conduit element with the following content:

   <http:conduit name="{http://my/wsdl}my-soap-endpoint.http-conduit";>
      <http:client AllowChunking="false"/>
   </http:conduit>

Finally, there's an element controlling use of WS-Addressing:

<wsp:Policy wsu:Id="addressingPolicy"
               
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
               xmlns:wsp="http://www.w3.org/2006/07/ws-policy";
               xsi:schemaLocation="http://www.w3.org/2006/07/ws-policy 
http://www.w3.org/2006/07/ws-policy.xsd";>
      <wsam:Addressing 
xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata";
                       wsp:Optional="true">
         <wsp:Policy/>
      </wsam:Addressing>
   </wsp:Policy>

Does any of that look suspicious?

> SOAP over HTTP messages have two Content-Type headers and SOAP action as a 
> separate header
> ------------------------------------------------------------------------------------------
>
>                 Key: CXF-687
>                 URL: https://issues.apache.org/jira/browse/CXF-687
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.1
>         Environment: NA
>            Reporter: Steven E. Harris
>            Assignee: maomaode
>            Priority: Minor
>
> Per the discussion in issue CXF-628, if I use SOAP 1.2 over HTTP, CXF 
> produces two Content-Type HTTP headers:
>   Content-Type: application/soap+xml; charset=UTF-8
>   action: "http://host/my-interface-service/some-operationRequest";
>   Content-Type: text/xml
> There should only be one Content-Type header -- the first one -- and the SOAP 
> action should be a parameter to that header, not a separate header, as 
> described in the SOAP 1.2 adjunct section A.3 on the "application/soap+xml" 
> media type and its optional "action" parameter:
>   http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#ietf-action

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to