On 09/01/2011 09:15 PM, Aki Yoshida wrote: > As Dennis says in his reply, the RM spec doesn't talk about this > transportation binding specific part. The reason, I suppose, is that > this is implicitly covered by the normal WS BP profile that recommends > the use of HTTP 202 if there is nothing to return.
Is this actually stated in BP? All I could find was that both 200 and 202 responses are allowed for an empty response to a successful request, with the comment (http://www.ws-i.org/Profiles/BasicProfile-1.1.html#HTTP_Success_Status_Codes): /Despite the fact that the HTTP 1.1 assigns different meanings to response status codes "200" and "202", in the context of the Profile they should be considered equivalent by the initiator of the request. The Profile accepts both status codes because some SOAP implementations have little control over the HTTP protocol implementation and cannot control which of these response status codes is sent./ So for BP compliance the client should not care which of these is returned by the server. > If I remember it correctly, Axis2/Sandesha uses HTTP 202 with no > content for all those responses (e.g., getting the http 202 response > at the http port when using a decoupled client port for the real > responses/acks). I can check this again. But maybe Dennis could also > verify how Axis2 and in particular Metro behave in this case. I'll try a decoupled client on Metro and post the results. - Dennis
