Easy way to collect fiddler log
This comes handy when you wanted to capture fiddler logs from a user machine where the issue occur and do not have fiddler installed. You need to install the fiddler if your motive is to just collect the logs and move on, then solution#2 is the recommended approach.
Solution #1:
Please download fiddler from the web: http://www.telerik.com/download/fiddler
1. Open Fiddler, In Tools->Fiddler Options->HTTPS, check “Decrypt HTTPS traffic”.
Click “Yes” on the prompt for trust Fiddler Root Certificate.
Click “Yes” to install the certificate.
Click “Yes” to confirm.
Click “OK” and “OK” to back.
2. Reproduce the issue, log down the time when the issue happen again. We may capture 2 or 3 times of the issue.
3. Stop Fiddler Trace: File->Capture Traffic F12, Save trace: File->Save>All Sessions. Save the trace out as .saz file
Solution #2:
1. Download the FiddlerCap – http://www.telerik.com/fiddler/fiddlercap
2. Select the options as you wish
3. Start Capturing 🙂
Advantages of fiddler cap:-
1) < 1 MB size (~330 KB)
2) ability to add comments and take snapshot
3) just do the stuff right
4) ability to clear WinINET cookies and cache (Tools > Clear..)
-
Recent
- The ID token is not yet valid. Make sure your computer’s time and time zone are both correct. Current epoch = 1689517128
- .NET Core – How to create a .NET GUI app which runs across the platform
- AKS 2022 updates
- Linux firewall and connectivity issues
- Microsoft Ignite (Sep22-24) event recap & On-demand sessions
- [Linux] Steps to install and configure sysstat package for monitoring.
- Azure Security Enablement – Centralized place for all the links
- Presenting tech session with stories [linkedin learning notes]
- gRPC using .NET core notes
- .NET in 2020 (Build recap)
- #KubeCon CNCF – North America 2019 watchlist
- AKS CLI Sheetcheat for the labs
-
Links
You must be logged in to post a comment.