We're having some strange issues when using the WebHttpBinding / WebInvoke and OneWay contracts (.NET 4.0). Without the "IsOneWay=true", everything is working great, but as soon as the one-way attribute is added, the WCF client always throws the
following protocol exception:
The one-way operation returned a
non -null message with Action ="
However, the interesting part is that invoking the service via Fiddler's request builder, the service responds correctly (returning a 202 instead of a 200). Is there some magic required to call one-way web methods from WCF clients,
or is this a known issue?
View Complete Post