[jira] Commented: (CXF-687) SOAP over HTTP messages have two Content-Type headers and SOAP action as a separate header

["Dan Diephouse (JIRA)" <ji...@apache.org>]

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

Dan Diephouse commented on CXF-687:
-----------------------------------

I'm trying to reproduce this but can't. Can you give us some more information?
- What version of CXF are you using? 
- Have you tried a SNAPSHOT version?
- Is this with the Jetty transport? Servlet transport? Or on the client side of things?
Thanks.

> 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.