From the comments, we’ve confirmed that your confusion arises from the fact that Sessions which have been deleted by filters cannot be recovered. The point of filters, beyond helping to limit what you see, is that they reduce Fiddler’s memory usage since unwanted data need not be stored. Obviously, if you’ve previously saved the traffic … Read more
This is simply a math problem. Assuming that content is available instantly (e.g. you’re playing it back from the AutoResponder) then the only delay is controlled by request-trickle-delay and response-trickle-delay flags. There are 1000 milliseconds per second. So, if you want to gate the connection to 1 megabyte per second, you would use a delay … Read more
You can do this in Fiddler using the following steps. Locate the request in fiddler that relates to the post – you should be able to see the URL you expect in the URL column. Select that line and the detailed view will open. There is a WebForms tab (inside “Inspectors”) that displays the POST … Read more
If the goal is to remove compression during the processing of a session: That’s what the “Decode” button on the toolbar does. That’s also what Rules menu > “Remove all encodings” does. If the goal is to remove the encoding after session processing is complete, select all of the sessions (CTRL+A) and use “Decode Selected … Read more
This has nothing to do with IIS7 Express and everything to do with the fact that you’re using loopback traffic. Ref: https://www.fiddlerbook.com/fiddler/help/hookup.asp#Q-LocalTraffic Click Rules > Customize Rules. Update your Rules file like so: static function OnBeforeRequest(oSession:Fiddler.Session) { if (oSession.HostnameIs(“MYAPP”)) { oSession.host = “localhost:portnumber”; } } Then, just visit http://myapp in your browser. Or use the … Read more
Try File > Preferences > Proxy Settings Host 127.0.0.1 Port 8888 and use http://localhost/myservice/myservice.asmx Here is a post that explain this a little bit more
Seems that your client didn’t try to connect via 1.2 Check: Tools > Fiddler Options > HTTPS It’s set to <client>;ssl3;tls1.0 Add “tls1.2” to the protocols list Edit: Refer to the image below for where to find the option:
Try the menu option Rules -> Hide CONNECTs
I had the same problem, but it turned out to be a chrome extension called hola (or Proxy SwitchySharp), that messed with the proxy settings. Removing Hola fixed the problem
You should start by reading this thread, which explains what a HTTP CONNECT Tunnel is: https://groups.google.com/forum/#!topic/httpfiddler/RCkzE3HhhxY Since you have enabled decryption, if you’re not seeing any HTTPS traffic in Fiddler, you either have a Filter enabled (click Help > Troubleshoot Filters) or you have not configured Windows to trust the Fiddler root certificate and hence … Read more