If you’re debugging Web service and you want to see what exactly reaching the service then you may need a network packet analyzer. In this article, you will see how to use Wireshark to inspect the incoming SOAP requests.
Wireshark is a network packet analyzer. It allows you to see the bits and bytes flowing through a network in human readable form. Without it, understanding a network communication exchange would be practically impossible.
At times, you may want to work with SOAP based web services, there are few tools available including WCF Test Client, Fiddler and SoapUI. In this post, I am going to see how do you use Fiddler to Compose HTTP SOAP Requests.
In my last post, I have explained “Hosting Windows Workflow as a WCF service in IIS” and I would strongly recommend reading it before you continuing further as the same service is used.
Fiddler is a free and open-source packet analyzer. It is used for network troubleshooting, analysis, software, communications protocol development and education.
Fiddler captures HTTP and HTTPS traffic data between browsers and servers. These data are extremely valuable for troubleshooting, performance tuning and system monitoring.
This article is a step by step tutorial to guide how to use Fiddler and capture HTTP Traffic.
Capturing of HTTP and/or HTTPS traffic may include private or confidential information, such as usernames, passwords or bank info. Use caution when entering in sensitive data while Fiddler is configured to capture traffic. If possible, use test or dummy data instead of confidential data while using Fiddler.
I have explained Hosting a WCF service in IIS in one of my previous post and I would strongly recommend reading it before you continuing further.
In this post, I am going to explain the way you can host Windows Workflow as a WCF service in IIS.