Binding uses an underlying protocol with no implicit return path
for messages. The message template for protocol identified by the "mythical-oneway" uri schema and specified in
wsdl 2.0 by the type="http://www.openuri.org/mythical-oneway/soap/" attribute and wsdl 1.1 by the onewayprotocol:binding transport="http://tempuri.org/mythical-oneway" element and attribute is
send DNSentry URI-path
message
POST /wsaService/service.ashx HTTP/1.1
http://tempuri.org/ServicePortType/EchoFault
HTTP/1.1 500
http://schemas.xmlsoap.org/ws/2004/03/addressing/fault
Robust in-only FaultTo
FaultTo specified.
Note that the previous scenario, a fault on the return path, is allowed when a FaultTo is specified. The messages flows in this pattern and the previous are valid.
POST /wsaService/service.ashx HTTP/1.1
http://tempuri.org/ServicePortType/EchoFaulthttp://microsoft.com/wsaService/service.ashxABCDEF
HTTP/1.1 202 OK
POST /wsaService/service.ashx HTTP/1.1
http://schemas.xmlsoap.org/ws/2004/03/addressing/fault
ABCDEF
HTTP/1.1 202 OK
POST /wsaService/service.ashx HTTP/1.1
http://tempuri.org/ServicePortType/EchoString*http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous*
HTTP/1.1 200 Accepted
http://tempuri.org/ServicePortType/EchoStringResponse
In-out ReplyTo
ReplyTo contains value.
Note this completely overrides the WSDL definition for soap bindings, as the WSDL says 1 soap request response mep is used with 1 HTTP protocol message.