Fiddler: Solution to the Task
Two weeks ago, we invited you on an exciting journey to explore Fiddler ??, a powerful web debugging proxy tool which allows us to capture??, inspect ??, and analyze web traffic ??, helping us identify potential issues and optimize the application.
We offered you a step-by-step task from setting up Fiddler to finding and reporting the defects:
Step 1??: Install Fiddler;
Step 2??: Configure Browser and Fiddler;
Step 3??: Capture Traffic and Analyze it;
Step 4??: Report Findings.
So, let's follow these steps.
?? Step 1: Installation
Pay attention that this tool requires payment, still you can get acquainted with it absolutely free during the 10 days of free trial version.
If you follow the link from the task https://www.telerik.com/fiddler - you'll find yourself on the Main Page (no surprise here).
After clicking [Try For Free] button you should select the version of the tool (there quite a lot of different Fiddler products) you would like to work with. Here are the options you will have:
What is the difference between these Fiddler Products? You can explore the the Fiddler family of products on the following schema taken from the official web site:
As you can see, we'll select between ? Fiddler Everywhere and ? Fiddler Classic. What is the difference between them? Again, let's have a look at the official documentation:
?? Fiddler Everywhere is a more focused implementation of Fiddler Classic that provides access to modern and supercharged features. Fiddler Everywhere works across all platforms equally well: macOS, Linux, and Windows, whereas Fiddler Classic solely supports Windows. In addition, Fiddler Everywhere has an improved and highly intuitive user interface, enhance organizational tools, and more powerful mocking capabilities.
So, we've decided to use ? Fiddler Everywhere. Once you've made your choice - you'll be suggested to read some learning materials about this tool:
After downloading the installation file, the easiest part starts - double click and install it on your computer. After installation you should create an account (if you do not have one):
After filling quite a simple form, and confirmation of your email - you are done with installation - feel free to explore the interface of this cool tool.
?? Step 2: Configuration
Fiddler configuration will differ from project to project, still there are some general actions to be done.
1??: Open the settings (gears icon) and click [Trust Root Certificate]:
领英推荐
2??: Mark checkbox with the label "Capture HTTPS Traffic" and click [Save] button.
3??: Look for the "Proxy Settings" section and enable the option to "Enable System Proxy."
With the proxy enabled, Fiddler Everywhere should automatically start capturing network traffic from various applications on your computer:
If needed, you can also configure the proxy port and other related settings in this section.
?? Step 3: Capture Traffic and Analyze it
Here is the logic is pretty simple:
3.1 -> ??Start Capturing Traffic:
With the proxy settings configured in your browser, start navigating to websites or using applications that use network connections. Fiddler Everywhere should capture and display the network traffic.
3.2 ->??Analyze Traffic:
Fiddler Everywhere provides various features to analyze captured traffic. You can inspect requests, responses, headers, and more. It also offers the ability to compose and modify requests, simulate different network conditions, and troubleshoot issues.
3.3 ->??Stop Capturing Traffic:
When you're done analyzing the traffic, you can stop capturing by disabling the proxy settings in your browser or by turning off the "Enable System Proxy" option in Fiddler Everywhere's settings.
?? Step 4: Report Findings.
You've found a defect? Well done!
Gather as much information as possible about the bug. This includes details such as the version of Fiddler you're using, the operating system, any error messages, steps to reproduce the bug, and screenshots or videos that illustrate the issue.
Then follow standard requirements to a good defect report.
When creating the bug report, be as clear and concise as possible. Include the following information: