HTTP Analyzer or Fiddler capturing API response – soapUI

Posted: February 27, 2012 in soapUI
Tags: , , , , , ,

THEN : Starting last year i wanted to use the Fiddler or HTTP Analyzer to capture the API request/response going out from my machine and all communication packet data between my local box & server. I tried a few combination with no success and in one odd cases my machine crashed [attaching soapUI process to HTTP Analyzer]. So decided to stay away from it.

NOW : Starting this year i tried the same (again) and finally succeeded. This blog talks about needed configuration.

Both Fiddler [Freeware] & HTTP Analyzer [Trial/Paid] are widely used tool for capturing the HTTP/HTTPS request/response data between 2 machine i.e., your local machine & web server. So captured data can be used to inspect traffic, act as proxy, analyze web application performance, highlight problem areas & to tamper incoming/outgoing data packets.

Assuming, by now, you have downloaded one of the tool we will go ahead with the specific configuration.

FIDDLER :

Fiddler Port Configuration

HTTP ANALYZER :

HTTP Analyzer to attach the process to monitor

After configuring the tools we need to Configure proxy settings in soapUI also.

soapUI Proxy Configuration :

soapUI Proxy toggle

soapUI preferences - Proxy setting

NOTE : If your Fiddler is configured to listen at some other port number then soapui should use the same port number.

All done! Now you can see the request /response getting captured in Fiddler/HTTP Analyzer. We can change the same request data and send it back to get the new response. Add some filter to block the response or change the response on meeting certain criteria.

So start fiddling your SOAP request/response data πŸ™‚ Until next blog happy Fiddling & happy Reading. Comments/Feedback/Inputs are always welcome.

Advertisements
Comments
  1. Astafyev Evgeny says:

    Hello, very good article, but i have a few questions. How can we use those tools to see incoming traffic? And second: wherein those tools better then standard soapUI Http Monitor – i didn’t get it.

    • What exactly you meant by “Other tools to see incoming traffic?” Fiddler and HTTP analyzer do this task (will capture complete details of request originated from your local box).
      HTTP monitor does provide the feature to capture the request/response however we can’t modify/tamper it (if i am not wrong). So that is where Fiddler comes into light πŸ™‚

  2. Astafyev Evgeny says:

    I have a service mock launched on my computer and someone sends message to it. And I want to see what is in it… That is the task. I didn’t get how to solve it with fiddler.

    • I would be interested to work on such a scenario. When i use mock service i always use localhost as endpoint. Hope you have configured both soapui proxy setting & fiddler correctly.

  3. YoU.Nike says:

    I am a newcomer to use fiddler,indeed, it can help us monitoring http(s) req & res. what’s more,
    to provide us with performance info, particularly response time, request information. I just filter special url through fiddler’s setting. checking xml and analyze info returned, as well as looking into issues if have. So it’s powerful to present some useful info so that help me analyze traffic which request sent out, how long does it call service, or calculate average response time…i am interested in the strategy & mechanism of the excellent tool. as for test scenario(s), here do hope people can share their good ideas. thanks PB!!

    thanks,
    Aaron

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s