无法获取NetTcpBinding的请求在提琴手现身 [英] Can't get netTcpBinding requests to show up in Fiddler

问题描述

我有了两个端点的WCF服务。一个与basicHttpBinding的，一个与NetTcpBinding的。这里是我的配置...

I have a WCF service that has two endpoints. One with basicHttpBinding and one with netTcpBinding. Here is my config...

<services>
      <service name="SomeService.Service">
        <endpoint address="" binding="basicHttpBinding" bindingConfiguration=""
          name="EndPointHttp" contract="SomeService.IService" />
        <endpoint address="" binding="netTcpBinding" bindingConfiguration=""
          name="EndPointTcp" contract="SomeService.IService" />
        </service>
</services>

然而，当我消费我试图之间比较差两个请求的服务。所以，我正在小提琴手做到这一点。我可以看到在提琴手的basicHttpBinding的要求，但我不能得到的net.tcp：//请求露面。我能做些什么，看看这个流量？

However, when I consume the service I am trying to compare the difference between to two requests. So I am running fiddler to do this. I can see the basicHttpBinding requests in Fiddler but I can't get the net.tcp:// requests to show up. What can I do to see this traffic?

推荐答案

提琴手是的 HTTP 的代理，所以它会它使用HTTP协议只捕获的请求 - 它不会捕获请求直接使用插座进行。您可以使用网络监视器或其他一些低级别的捕捉工具，要做到这一点，但界面是不是像你一样，你可以用来与小提琴手之一。

Fiddler is a HTTP proxy, so it will only capture requests which use HTTP protocol - it will not capture requests made using socket directly. You can use the Network Monitor or some other low-level capture tool to do that, but the interface is not as nice as the one you may be used to with Fiddler.

此外，作为中指出由拉吉斯拉夫Mrnka另一个答案，你会看的 .NET消息帧和二进制XML编码，所以，除非你熟悉他们大部分捕捉看起来像废话。

Also, as pointed out in another answer by Ladislav Mrnka, you'll be looking at the binary bytes for the .NET Message Framing and the binary XML encoding, so unless you're familiar with them most of the capture will look like gibberish.

这篇关于无法获取NetTcpBinding的请求在提琴手现身的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！