I find myself applying the same filters again and again on each launch of Fiddler (I mean the filters listed below the list of requests). I think it would be really great if you could allow the restoration of previously applied filters (e.g. by having a save/load filters option). Also, allowing to filter out by "Request Method" would be great too. Congratulations on this tool, by the way. It is really great. :)
I'm seeing the exact same issue. I then added the -dpiAware switch to the shortcut which helped some but parts of the app are still displaying wonky. See screenshot.
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.
Where specifically did you set the filter? If you right-click the Session and choose "Properties", what are the flags on the unexpectedly-visible Session? (By default, Fiddler doesn't hide sessions which resulted in HTTP Protocol Violation errors).
Problem: Today you have to leave the application and discover Fiddler listening IPs using ipconfig or "netstat -na | findstr 8888". Having the IP address list that the tool is listening will allow a fiddler user to not leave the application to discover all the IP addresses that the tool is waiting connections. Specially useful when you need to configure the proxy settings on and Android or IOS device and need to know what IP address to point the HTTPS proxy. I'd expect to see all the bindings somewhere on the bottom toolbar. A nice addition would be also the URLs to Fiddler Echo service to be shared with users that need to install the root certificate on devices and use Fiddler as a proxy for troubleshooting.
I've seen this happen once in a while too. Do you have any extensions installed?
FWIW, one reason that the RAW Inspectors are so rough is that I never used them, even though I suspect telemetry would show that they're pretty popular. The Raw Inspectors are among the few remaining Inspectors that don't override the AssignSession() method, but should. That will allow setting the Headers, Body, and ReadOnly state in one shot instead of performing three updates. This should take no more than a few minutes for Telerik to change.
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
Not much more to say. Fiddler on Windows is absolutely awesome, but nothing comes close on Max OS X. Please, please, please offer a native Mac OS X version. I'd hiply pay 4100 or more for it. I'd even pay that for an annual subscription.
I'm running the latest Fiddler's mono version and it would be great to be able to capture WebSockets traffic on this version. I know it is possible on the Windows version.
New compression from Google - better than gzip. Supported in Chrome and FF. See site https://www.netwarc.nl/ for an example. Fiddler is unable to decompress the response content. Also see http://www.omgchrome.com/brotli-http-compression-coming-to-chrome/ and https://textslashplain.com/2015/09/10/brotli/
I access APIs that are IP restricted. Previously, I would set the proxy through IE and then load up Fiddler and start issuing tests through the composer. Now, as soon as I start Fiddler, the System Proxy settings are reset to 127.0.0.1. This happens if I start Fiddler once the proxy settings have been made, or if I set the proxy while Fiddler is running (the System Proxy will go to 127.0.0.1 once Fiddler posts the 'A system proxy was changed. Click to reenable Telerik Fiddler capture' message). It used to work perfectly, but I updated my Dell laptop recently and now Fiddler is not working with the Proxy correctly. This makes Fiddler impossible to use with a Proxy. Is there any work around? Is there a way to explicitly set the proxy IP within Fiddler?
I find having Capture on when you start Fiddler a pain since almost always one of the first things I have to do is turn it off. I'd like the option to just have it off on startup.