So I'm finally trying Everywhere vs. Classic and the first thing I've noticed is there doesn't seem to be any way to set up Everywhere so it doesn't show all the annoying, distracting traffic I don't care about and don't want to see (e.g. callouts by Microsoft Outlook, Teams, Chrome extensions, etc.)
This was a really important option. Surely they didn't take it away? With all the extraneous traffic flowing through, the things I really want to see get lost in the noise.
For my use case, it is NOT helpful to filter for ONLY certain URLs, etc. I just need to filter things OUT.
Please, what am I missing?
1 Answer, 1 is accepted
Hello Mark,
Thank you for giving a chance to the Fiddler Everywhere application!
There are several approaches available in Fiddler Everywhere to filter the captured traffic as follows:
1. You can use the Rules feature to create custom rules that show or hide specific traffic based on complex matching criteria. To filter out the captured traffic, you can use process name, host, URL, path, HTTP method, request and response bodies and headers, and many more matching conditions (including a combination of several conditions). For your convenience, I am attaching a set of filtering rules as an archive that contains a FARX file (called filter_rules.zip), which you can import in the Rules tab of Fiddler Everywhere through the import button (refer to the screenshot below)
Learn more about how to create and use rules in Fiddler here...
2. The filters feature allows you to create complex filters for all URLs except those you want to see. The filter feature supports regular expressions and multiple matching conditions. For example, you can filter by URL, process name, client and remote IPs, etc.
More information about the filter and the matching options is available in the following documentation articles:
https://docs.telerik.com/fiddler-everywhere/modify-and-filter-traffic/filter-traffic
https://docs.telerik.com/fiddler-everywhere/knowledge-base/final-and-non-final-actions#conditions
3. You can bypass a list of endpoints so their traffic does not go through the Fiddler proxy. You can easily add new endpoints to the bypass list through the Live Traffic context menu - the new entries will be added to the bypass list, which you can see in Settings > Connections > Bypass Fiddler for URLs .. option.
Learn more about bypassing the proxy here...
4. Lastly, you can use alternative capturing modes instead of the system capturing mode. Modes like independent browser capturing or terminal capturing will allow you to capture traffic from a sandboxed environment, which will spare you from capturing traffic from all applications (that respect the system proxy—when system capturing mode is used).
Learn more about the capturing modes in Fiddler Everywhere here...
Regards,
Nick Iliev
Progress Telerik
Rank 1
Hey Mark,
Note that some actions, like "Do Not Show," have a final nature. This means that once a similar rule is hit, no other actions or rules (located lower in the queue) will be executed. The final rules have a warning message that explains their behavior.
In your case, one possible reason the rule does not work is that another action or rule triggers a final action prior to that rule. If that is not the case (and, for example, the rule is not working even if it is the only active rule in the queue), then you could send us the rule structure of the rule and any related details so that we can run further tests.