Troubleshooting and debugging Web applications starts with a basic question: what does the client experience, and what happens on the server? This article helps answer one of the first questions a troubleshooting professional would ask: what does the client “see” from the server?
Screenshots from the browser or client sometimes provide this answer. But many times, HTTP requests leave the client and responses are received long before a human could collect screen captures. Or maybe it is the sequence that matters, not only one request. And, with AJAX, a client may not display anything relevant at all. So, here we are: we need to collect some HTTP traces; an HTTP traffic recording for investigation.
As a browser add-on, HTTP Watch helps collect all information needed, with minimal interference and in a consistent manner. The steps:
Fiddler is known as THE tool to be used in troubleshooting from the client side. It has been long used by engineers and developers for its features. But there are a couple of points I want to emphasize.
Steps to take:
Finally, using the features of the browser will do, assuming that the client is a browser, of course. There are some drawbacks, such as format inconsistencies from browser to browser.
We need to collect a HAR, HTTP Archive. My personal favorite is Firefox. Chrome may be fine. There is glitch in Egde/IE – they would not start developer tools with a new empty tab.
All the best!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.