开发者

Can't get netTcpBinding requests to show up in Fiddler

开发者 https://www.devze.com 2023-03-12 10:06 出处:网络
I have a WCF service that has two endpoints. One with basicHttpBinding and one with netTcpBinding. Here is my config...

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

<services>
    开发者_如何学Python  <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>

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?


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.

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.


Fiddler is HTTP sniffer not TCP sniffer. You can see only HTTP and HTTPS communication in fiddler. If you want to see messages passed over TCP you must use another tool working on lower level. For example WireShark but be prepared that you will see only some binary data.


Fiddler is an HTTP debugger. If you're not using HTTP, such as with a netTcpBinding, you won't be able to capture traffic with it. You could try Wireshark or something similar.


If you are interested into how the actual messages look like then try using Service Trace.

https://msdn.microsoft.com/en-us/library/ms732023%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396

0

精彩评论

暂无评论...
验证码 换一张
取 消