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
To view the message contents you must add a source for System.ServiceModel.MessageLogging in your configuration file. The message tab in the Trace Viewer will show the full message for a particular service call. Here is a sample configuration file: <configuration> … <system.diagnostics> <sources> <source name=”System.ServiceModel” switchValue=”All” propagateActivity=”true”> <listeners> <add name=”traceListener” /> </listeners> </source> <source name=”System.ServiceModel.MessageLogging” … 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
What’s the client of the web service? ASP.NET? ASP.NET traffic isn’t proxied unless you configure ASP.NET to use a proxy. It’s possible/likely that the app.config or machine.config changed such that traffic is no longer getting proxied? You should have a look at this section: http://www.fiddlerbook.com/fiddler/help/hookup.asp#Q-DOTNET
The Fiddler FAQ gives the answer to this. You essentially route your HTTP traffic through Fiddler (i.e. Use Fiddler as a proxy). Here’s some links that will help: Fiddler Web Debugging – Configuring Clients Which in turn links to here: Take the Burden Off Users with Automatic Configuration in .NET You can achieve this via … Read more
I found the solution at this fiddler2.com page Why don’t I see traffic sent to http://localhost or http://127.0.0.1? Internet Explorer and the .NET Framework are hardcoded not to send requests for Localhost through any proxies, and as a proxy, Fiddler will not receive such traffic. The simplest workaround is to use your machine name as … 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
Your simplest approach would be to right-click the Web Sessions list’s column headers and choose Customize Columns… from the menu. From the Collection dropdown, choose the Session Timers option and then select the timer of interest in the Timer Name dropdown.
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:
If you want to look at the traffic with Fiddler, you probably want to go the route of changing the machine.config file so that all .NET applications will send traffic through Fiddler. This helps ensure that you capture data from processes running in services, etc. Open machine.config in the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config. Note that if you … Read more