cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse (JIRA)" <>
Subject [jira] Created: (CXF-633) SOAP 1.2 action header is sent incorrectly
Date Fri, 04 May 2007 10:16:15 GMT
SOAP 1.2 action header is sent incorrectly

                 Key: CXF-633
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.0-M1, 2.0-RC
            Reporter: Dan Diephouse
             Fix For: 2.0

>From Steven Harris on the user list:

My CXF client is using SOAP 1.2 over HTTP. I have specified a SOAP
action in my WSDL for my one bound operation. This action value is
getting sent as follows:

| POST /my/service/location HTTP/1.1
| Content-Type: application/soap+xml; charset=UTF-8
| action: "http://my/operation/action"
| ...

I would expect the SOAP 1.2 treatment of the action parameter to be
adjoined to the Content-Type header, like this:

| POST /my/service/location HTTP/1.1
| Content-Type: application/soap+xml; charset=UTF-8; action:="http://my/operation/action"
| ...

That's how AXIS2 does it, anyway, and it matches my reading of the
SOAP 1.2 specification, Part 2, Adjuncts┬╣:

,----[ Section 6.5.2 SOAP Action Description ]
| Many SOAP 1.2 underlying protocol bindings will likely utilize the
| "application/soap+xml" media type (described in A. The
| application/soap+xml Media Type) to transmit XML serializations of
| SOAP messages. The media type specifies an optional action parameter,
| which can be used to optimize dispatch or routing, among other things.

Does CXF's use of the "action" header in the first example above
conform to SOAP 1.2?

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

View raw message