I came across an article (https://jimshaver.net/2015/02/11/decrypting-tls-browser-traffic-with-wireshark-the-easy-way/) describing how Wireshark is able to decrypt SSL encrypted network traffic by making use of a feature in Mozilla Firefox and Google Chrome: If a system environment variable named SSLKEYLOGFILE is set to a valid filename, those browsers will write SSL key data to the file. Wireshark, in turn, uses to the contents of the file to decrypt SSL encrypted packets that it captures. Assuming it's technically possible, it would be great if Fiddler could do the same as an alternative to use the Fiddler Root certificate.
See attached screenshot. Please confirm and fix the certificate.
The Header length is easily accessible from script/extensions, but it's not easily found just by looking at the Inspector. It should be exposed somewhere on the Headers inspector.
So i downloaded fiddler and I was trying to change my name on Fortnite and I trusted the certificate and did everything correctly when restarting fortnite it asks me to log in and when i try it says its unable to login to fortnite and i shout try agian later it doesnt work and its really annoying please reply as fast as you can.
At some point, the dialog box which displays HTTP Protocol Violations seems to have disappeared? Protocol violations still appear within the Web Sessions list (e.g. showing sessions with a light-yellow background) but the standalone Window doesn't seem to be around anymore. This makes it much harder to discover these important problems.
This seems to happen a non-trivial number of times, and it causes clients and scenarios to fail in surprising ways.
1. Open a SAZ file. 2. File > Save. Use the same name Result: Prompted twice before saving. [Window Title] Confirm Save As [Content] QuanticFoundary-EdgeFails.saz already exists. Do you want to replace it? [Yes] [No] --------------------------- (no title on this window prompt, another bug in itself) --------------------------- File C:\Users\ericlaw\Documents\Fiddler2\Captures\QuanticFoundary-EdgeFails.saz already exists. Do you want to replace it? --------------------------- Yes No ---------------------------
We use fiddler to reverse proxy requests to out dev environment back to our development machines while working So normally microsite1.dev.mycompany.com resolves to 192.168.1.639 but when fiddler is capturing it resolves to 127.0.0.1 so that we can debug and do development on specific microsites without having to have our entire environment replicated locally. This is great until fiddler stops capturing unexpectedly, which isnt always obvious. It would be useful if a warning could pop up, or an audible alert would sound to let us know that something went wrong and the capture had stopped.
It would be lovely if fiddler could capture traffic when opening it without having to close the browser and open the browser again.
Since the primary use-case for Fiddler is to observe the raw traffic within requests, I believe most Fiddler users would benefit from having the default view set to Inspectors > Raw when launching the application. At least for the Response data.
Microsoft telemetry calls to v10.vortex-win.data.microsoft.com bypass the filters and add noise. If my filter says only show localhost, I don't expect to see calls to Microsoft.com.
It's huge, doesn't have anything to do with Fiddler besides being a Telerik product, and I have no interest in it after having used previous Telerik toolkits. People already deal with ads when consuming content. Don't add them to shit we use when doing work.
Using the exported wcat file as test automation input, basically read and issue each and every http request from the wcat script, However, the put and delete message was missing
The program is always stuck to death recently and the port 8888 is occupied，change other port can't catch the reqeust。 command netstat -ano|findstr 8888 can't find 8888 is occupied.
There should be an option to limit bandwidth for certain request responses and not all in the way we have Autoresponder implemented. It should match the rule and apply the limit accordingly. So that we can check how a particular API from that domain is only behaving instead of simulating the entire sessions from a particular domain.
Microsoft appears to have moved their web developer documentation from MSDN to MDN, making searches from Fiddler's toolbar return useless results. Please consider making the Search Cue text and Search URL configurable via a preference and set the defaults to "Search MDN" with a URL of https://developer.mozilla.org/en-US/search?q=$SEARCHTERMHERE&topic=apps&topic=html&topic=css&topic=js&topic=api&topic=canvas&topic=svg&topic=webgl&topic=mobile&topic=webdev&topic=http&topic=webext&topic=standards