Will there be a way to filter traffic while capturing to avoid "spamming" of the logs?
p.s using Fiddler on Mac.
I have followed the documentation and exported the fiddler cert to my machine, did the trust certificate through windows cert management and then in Settings for Chrome and Firefox I added the cert but still I get security denial when hitting any https site with Decrypt HTTPS traffic checked.
Anyone can help?
Thanks,
Maark
I'm using Fiddler to look at requestsare being made by a WPF/WCF application I'm developing in Visual Studio.
I changed the app.config file so that the WPF project makes requests to http://localhost.fiddler:50000/ instead of the usual http://localhost:50000/, but for each request, Fiddler shows multiple entries.
See the attached screenshot, where you can see three entries for the call I made to CustomerService.svc for a customer list. You can tell this is the list call from the size of the return data.
If I add breakpoints in VS, I can see that there is actually only one call being made, but Fiddler shows three.
Anyone able to explain why. This is making debugging very confusing.
Thanks
We have a web based application that renders inside an iFrame. When using Fiddler and decrypting HTTPS, there is one iFrame that generates the message "The security certificate presented by this website was not issued by a trusted certificate authority". If we uncheck the decrypt option or use the application without Fiddler running we have no errors. Looking at the URL it is trying to browse to a website that has a Fiddler DO_NOT_TRUST certificate in the user personal certificate repository. I have clicked on the Actions button on the HTTPS tab and chosen the "Trust Root Certificate" option but that made no difference. Any ideas why this one site would reject the Fiddler certificate?
Thanks in advance

Hi,
I have problem download the certificate on any mobile (iOS and android) at work.
I made the configurations on my phone but I still can't download the certificate on this address:
http://ipv4.fiddler:8888/ (Device : Samsung S8, S7, Iphone X, iphone 6)
the Fiddler Echo Service dos not load
the "Decrypt HTTPS" option in Tools -> Options -> HTTPS is checked.
NB (At home it works without problems with the wifi)
Has this to do with the corpatret wifi that does not allow this?
Thanks

Hi Friends,
I am using a Chrome browser and when I turn Capturing On I notice that I am unable to see the http request data from my Restful API and my page also does not return any data. I notice that when i open another Chrome Browser the URL says Not Secure and their is a message in the body of the page that reads... Your connection is not private. I dont have a clue as to what is going on so I just titled my question as this being an issue with the proxy. Thanks for any help !

I have to trace incoming https requests using fiddler. As per docs, we have to use fiddler as reverse proxy for which we need to make a change in registry.
In organization, touching registry manually is not allowed. Is there anyother way to enable the reverse proxy feature. Is there any button available in fiddler through which changes can be done automatically.
Please suggest. I need this on urgent basis.
Hi guys,
I'm getting the following error:
CONNECT :443 HTTP/1.1Host: :443A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below.Version: 3.3 (TLS/1.2)Random: 0F 42 E4 A0 84 A5 05 4B 54 8C 2C 2B A1 F4 01 B8 9D 81 9A A8 74 FE 24 E8 46 15 19 68 3C BC 0E 01"Time": 16-07-2055 03:21:19SessionID: emptyHTTP/1.1 200 Connection EstablishedFiddlerGateway: DirectStartTime: 19:37:45.587Connection: closefiddler.network.https> HTTPS handshake to (for #1) failed. System.IO.IOException Received an unexpected EOF or 0 bytes from the transport stream.
I have trusted the fiddler root certificate, imported it via mmc. Further more I have set fiddler to ignore certificate errors, and enabled the following protocols:
<client>;ssl2;ssl3;tls1.0;tls1.1;tls1.2
I'm using fiddler 4.5, but have also tried with version 2.
I also tried searching for this issue, but no solution seemed to present itself. Usually adding tls1.2 worked for people, but not in my case :(
