So, first let me apologize for being in way over my head. Now that that's out of the way....
I was wondering if someone could maybe help me explain why an API call made from .NET (specifically the Invoke-RestMethod cmdlet in powershell) might return a 401 Auth Error when executed without fiddler, but return data as expected while fiddler is open? This behavior occurs using both HTTP and HTTPS (I found an article from way back mentioning Fiddler used a specific TLS regardless of the client request, but this does not seem to be the case anymore).
I've typically only interacted with this particular API via PHP and cURL, but I needed a windows application.
It would seem to me that the explanation is that Fiddler is somehow modifying the request my application is sending, but I have no idea how to look for that.
If this isn't the correct place for this question, my bad.
Hello forum
does FiddlerCap capture all 7 OSI Layers or only "connections" ?
Thank you!
Joe


Hi,
I'm trying to watch the API calls that my app is doing using Fiddler, I was able to do it in Android Phone, iOS, but not in Android TV box.
For some reason, the .crt file is not being installed in the device. When I try to install it, the box shows me a message saying "Certificate not installed", so I'm not being able to capture the API calls.
Did someone make Fiddler work in Android TV devices?
Thanks.
Hi,
I am a newbie in using fiddler. I was trying to capture the HTTPS traffic from android app. I have installed the fiddler root certificate successfully on my android device but not able to capture the https traffic but i see http calls going through tunnel.
Fiddler version : v5.0.20192.25091
Android OS version : 8.1.0
Please see the attached image for the fiddler settings applied and let me know if needed any more information.
Thanks

I downloaded the latest version on website for Fiddler Everywhere Beta (v0.10.2) and upon fiddling around with it I found this reproducible issue. I'm running macOS Catalina (v10.15.3).
When you quickly and repeatedly click on the toggle for live traffic capture, fast enough that you don't let the toggle complete its animation / switch to either state, more than a couple of times (perhaps 10 times or more), the UI keeps toggling when you do and will settle on one state when you stop clicking.
But after a few seconds, the toggle will starting switching again. Sometimes it takes more than a few seconds. It toggles a couple of times, and even if it finally stops itself at "on" state, the traffic is no longer captured.
A user might not try to deliberately break the app like this, but perhaps there's something async going on with the UI that makes the actions happen later and also break the capture part.
Not sure what kind of system details might be required, but here's some generic info:
Application version: v0.10.2
OS version: Catalina (v10.15.3)
Processor: 2.3GHz Intel i5 (8GB DDR3 RAM)
