WCF WebInvoke + IsOneWay [英] WCF WebInvoke + IsOneWay

问题描述

在使用WebHttpBinding/WebInvoke和OneWay合同(.NET 4.0)时，我们遇到了一些奇怪的问题.没有"IsOneWay = true"，一切工作都很好，但是一旦添加了单向属性，WCF客户端就会始终抛出 以下协议异常:

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 ="

但是，有趣的部分是，通过Fiddler的请求构建器调用服务，该服务正确响应(返回202而不是200).从WCF客户端调用单向Web方法是否需要一些魔术， 还是这是一个已知问题?

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?

谢谢！

Thanks!

推荐答案

碰碰运气...有人对此问题有想法吗?

Just a bump...anyone have any thoughts on this issue?

TIA ...

这篇关于WCF WebInvoke + IsOneWay的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！