[
https://issues.apache.org/jira/browse/CXF-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-687:
----------------------------
Priority: Critical (was: Minor)
Affects Version/s: (was: 2.1)
2.0
2.0.1
Fix Version/s: 2.0.2
The PolicyUtils is blindly copying the ClientPolicy.getContentType() stuff from
one to another without checking the isSetContentType(). Thus, there is always
a "text/xml" content type.
The HTTPConduit is calling request.setHeader("Content-Type", ..) with that
value instead of calling message.put("Content-Type", ...) so it can be merged
with the charset and stuff later.
> 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.0, 2.0.1
> Environment: NA
> Reporter: Steven E. Harris
> Assignee: Daniel Kulp
> Priority: Critical
> Fix For: 2.0.2
>
>
> 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.
