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. :)
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.
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.
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.
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'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.
I develop a lot of extensions for Fiddler. Some of them are public (http://github.com/vcsjones/FiddlerCert) , others are private to my organization. Currently Fiddler4 is built against the .NET Framework 4.0. I don't want my extensions to depend on a different version of the .NET Framework than what Fiddler requires, which lowers the burden of distributing them. If Fiddler runs, then I can be sure my 4.0 extension will too. It would be handy if Fiddler updated the .NET Framework version requirement. It would 1) give you guys more Framework to work with, and 2) allow me to up the framework requirement of my extension while still meeting the bare minimum that Fiddler itself requires. There is a considerable amount of new cryptographic faculties in the .NET Framework 4.6.1 that would be handy for my uses.