When I click on the packet in the top frame (the blurred blue line, no you can't have my IP address), the entire protocol stack is displayed. Then I can run through the forms on the client application, hit submit and my message appears in the Wireshark UI. The service asmx file is called MyService.asmx, so the filter looks like this: contains 'My Service.asmx' Not only that, but it knows how to reassemble muti-packet messages so you can see each individual packet that makes up an HTTP request or response but also the complete message.Īll I had to do was install Wireshark on the web service's server and set the filter to look for any request for my web service.

The detail is awesome, you can see the entire protocol stack for each packet: Hardware, Ethernet, IP, TCP, HTTP and drill down into the details of each. This is an excellent tool for capturing network traffic. What I wanted to do was capture the request and be able to play it back to my web service.

Before the service is called you have to fill in several pages of forms very tedious from a testing point of view. I don't have any access to the client except via its UI. I'm working on a web service that processes requests from an existing application.

Wireshark vs fiddler 2