W3C home > Mailing lists > Public > public-ws-addressing@w3.org > August 2006

Re: [wsi_wsbasic] Re: NEW ISSUE: wsa:Action header and SOAPAction HTTP header are of different types but required to be the same

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Tue, 08 Aug 2006 11:02:08 -0700
Message-ID: <44D8D1A0.20909@oracle.com>
To: Christopher B Ferris <chrisfer@us.ibm.com>
CC: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>, WSI Basic <wsi_wsbasic@lists.ws-i.org>

+1
We may also want to include this in our 'backward compatibility' 
section/bucket.

-Anish
--

Christopher B Ferris wrote:
> 
> Makes sense to me.
> 
> Proposal:
> 
> Add new section, new Rnnnn and accompanying rationale.
> 
> X.x Valid Range of SOAPAction When WS-Addressing is Used
> 
> There may be some confusion as regards to the range of valid values for 
> SOAPAction when WS-Addressing
> is used, given that the SOAP 1.1 specification permits the use of 
> relative URIs. When composed with
> WS-Addressing, the valid range of values of SOAPAction is limited to 
> either an absolute URI that
> matches the value specified for wsa:Action, or the empty string ("").
> 
> Rnnnn When wsa:Action MAP is present in an envelope, the containing 
> MESSAGE MUST specify a SOAPAction
> HTTP header with either a value that is an absolute URI that has the 
> same value as the value of the wsa:Action MAP,
> or a value of "".
> 
> Cheers,
> 
> Christopher Ferris
> STSM, Software Group Standards Strategy
> email: chrisfer@us.ibm.com
> blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
> phone: +1 508 377 9295
> 
> Anish Karmarkar <Anish.Karmarkar@oracle.com> wrote on 08/08/2006 
> 12:37:27 PM:
> 
>  > Basic Profilers,
>  >
>  > WS-Addressing wsa:Action header block is of type absolute URI [1].
>  > SOAPAction HTTP header [2] is a URI reference (but not required to be
>  > absolute). Per the WS-Addressing SOAP binding [3] the two must either be
>  > the same or the SOAPAction HTTP header value must be "".
>  >
>  > It therefore follows from the three specs referenced above that any
>  > SOAP/HTTP message that uses WS-Addressing cannot have a SOAPAction HTTP
>  > header with a value that is not an absolute URI (with the exception of
>  > ""). I.e., relative URIs (other than the empty string) are prohibited.
>  >
>  > The WS-Addressing WG felt that this was clearly stated by the three
>  > specifications involved, but there were concerns expressed within the
>  > WS-A WG that this may not be very obvious to the readers (who have to
>  > connect the dots). It was felt that such clarification fell within the
>  > purview of WS-I Basic Profile WG and the WS-A WG wanted to bring this to
>  > your attention.
>  >
>  > Thanks and regards.
>  >
>  > -Anish Karmarkar
>  > on behalf of WS-Addressing WG
>  > --
>  >
>  > [1] http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#msgaddrprops
>  > [2] http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383528
>  > [3] http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/#s11extdesc
>  >
Received on Tuesday, 8 August 2006 18:03:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:14 GMT