IT:AD:Fiddler:HowTos:Track WCF Traffic

The SVCTraceViewer is good for some things…but isn’t much good for viewing the actual contents of a message (unless I missed something?)

For that, you can either bang away at soapUI – or whip out Fiddler and check the messages being sent back and forth.

Except that there’s a catch worth knowing about: fiddler doesn’t track localhost or 127.0.0.1

If you’re using Fiddler with a localhost or 127.0.0.1 address you’ll find that Fiddler will not monitor requests. The reason for this is that local addresses typically bypass any proxies (and the network adapter in general) and so localhost or 127.0.0.1 doesn’t show up.

Luckily there’s an easy workaround for this: Instead of using a local address use the NetBios Machine name or the local IP address

Once you’ve changed the clients endpoint address…you get tracking (well…that and possibly proxy setup in some cases…see below).

Src:

http://www.fiddler2.com/fiddler/help/

http://msdn.microsoft.com/en-us/library/Bb250446.aspx

http://www.west-wind.com/weblog/posts/596348.aspx