Fiddler runs on your PC and monitors all traffic between your Web browser and the Internet. When captured and saved this traffic can be a useful source of problem resolution information.
Reminder: It is important to clear the browser cache before generating a fiddler log.
|Does it have to be installed separately? If yes, where do you get it from?||Yes. Fiddler can be downloaded from http://www.fiddler2.com/fiddler2/|
|How you turn it on / start it?||Run the Fiddler application on the same PC as the browser. To start capturing traffic, select Capture Traffic from the File menu.|
|How you turn it off / stop it?||Deselect Capture Traffic from the File menu or close the Fiddler application.|
|Are there performance ramification in using it?||If run for long periods of time it may develop some memory or disk space problems. Normally you would only run it while reproducing a particular problem.|
|How is it typically used to isolate problems?||Fiddler is a proxy that sits between the browser and the server an captures all traffic between the two. It makes it possible to see exactly what is, or isn't, being sent between the two. In addition, the sessions can be saved for later playback making it possible to reproduce and diagnose a problem remotely, without needing a VPN or host connection.|
|What sort of information might you be asked to send to Axes support?||You may be asked to send a Fiddler log. This would involve starting Fiddler and then turning on Capture Traffic just before reproducing the problem. After the problem has been reproduced you save the traffic details to a Session Archive file (*.saz) by selecting File > Save -> All Sessions. Send the resulting .saz file to aXes support.|
|A summary of typical usage of Fiddler?||Open your web browser and clear your browser cache.
Close your web browser.
Start Fiddler and turn on the Capture Traffic option.
Reproduce the problem in your web browser.
In Fiddler - select File > Save -> All Sessions.
Send the resulting .saz (Session Archive) file to support.