Under Review
Last Updated: 14 Oct 2019 05:45 by Oozma
Imported User
Created on: 16 Jan 2018 05:59
Type: Feature Request
19
Make sure that filters apply to MS telemetry calls (e.g. v10.vortex-win.data.microsoft.com)
Microsoft telemetry calls to v10.vortex-win.data.microsoft.com bypass the filters and add noise. If my filter says only show localhost, I don't expect to see calls to Microsoft.com.
21 comments
Oozma
Posted on: 14 Oct 2019 05:45
Latest version of fiddler >v5.0.20194.41348 contains an additional option in the list for "If protocol violation are observed" named "Do nothing". Select that and telemetry requests are hidden.
Imported User
Posted on: 03 Aug 2018 05:00
This can be done in the fiddler script editor, just dont display sessions where the hostname contains "vortex"
Imported User
Posted on: 29 May 2018 05:00
>or you could possibly write code that masks out the SessionFlags.ProtocolViolationInRequest flag on requests you don't care about.

My point was that fiddler already knows about "requests I don't care about"...these are in the Filters., so it seems logical that fiddler applies filter rules to protocol violations.

For now I have ignored all protocol violations, editing OnPeekAtRequestHeaders resulted in everything being filtered out. Probably something I did wrong, but I haven't time to investigate at the moment.
Imported User
Posted on: 17 May 2018 05:00
Would love to get this fixed. None of the suggestions fix this, or at least need better explanations, I was unable to get onpeekheaders to do fuck all.
Imported User
Posted on: 15 May 2018 05:00
Same shit for me. I couldn't find a way to solve it yet.
Eric
Posted on: 15 May 2018 05:00
Okay, I spent a few minutes looking at this.

> if I have filters enabled, nothing should bypass those filters... it's just bad manners.

Fiddler's filters deliberately ignore cases where there's good reason to believe that something has broken that might not be failing without Fiddler in the way. Otherwise, running Fiddler could cause side-effects that would be nearly impossible to troubleshoot.


Now, unfortunately, because of how stealth is implemented, it's not applied to cases where there's a protocol violation in the Request or Response. The test in the ShouldBeHidden function probably should be changed to respect stealth because it's a non-default override.

As a user, to make these lines go away, you could either change Tools > Fiddler Options > General > "If protocol violations are observed" to "Do Nothing" (which is sad, because protocol violations ARE generally very useful), or you could possibly write code that masks out the SessionFlags.ProtocolViolationInRequest flag on requests you don't care about. Or you could hack together code that just hides them periodically. (eww).

The script sample earlier has two typos-- the function is named uriContains and the word stealth needs to be in lowercase.

For best results, put it inside OnPeekAtRequestHeaders:

if (oSession.uriContains("watson.telemetry.microsoft.com")) { oSession["ui-hide"] = "stealth-boring boring boring...."; }
Imported User
Posted on: 22 Apr 2018 05:00
I have the same issue and it drives me crazy. I have tried just about everything but these still show.
Imported User
Posted on: 22 Mar 2018 05:00
I tried adding the ui-hide member on the session in the OnBeforeResponse handler using Eric's STEALTH suggestion. Fiddler threw a compilation error, "Objects of type 'Fiddler.Session' do not have such a member."

Using automatic syntax completion and comparing other code in CustomRules.js, the urlContains function was apparently renamed uriContains. Fiddler didn't complain after I used the latter function name.

I agree with Greg Woods' comment about filters actually filtering what you tell them to. Perhaps an additional UI option to show/hide protocol violations would be in order.
Imported User
Posted on: 22 Mar 2018 05:00
I tried adding the ui-hide member on the session in the OnBeforeResponse handler using Eric's STEALTH suggestion. Fiddler threw a compilation error, "Objects of type 'Fiddler.Session' do not have such a member."

Using automatic syntax completion and comparing other code in CustomRules.js, the urlContains function was apparently renamed uriContains. Fiddler didn't complain after I used the latter function name.

I agree with Greg Woods' comment about filters actually filtering what you tell them to. Perhaps an additional UI option to show/hide protocol violations would be in order.
Imported User
Posted on: 22 Mar 2018 05:00
An example of the amount of crap filling my fiddler sessions
Imported User
Posted on: 15 Mar 2018 05:00
My sessions list is being filled with Windows 10 telemetry calls, all with 408 errors. Even trying to remove them using fiddler script (a workaround) has failed.

Quote: "(By default, Fiddler doesn't hide sessions which resulted in HTTP Protocol Violation errors)."

IT SHOULD.

if I have filters enabled, nothing should bypass those filters... it's just bad manners.
Imported User
Posted on: 08 Mar 2018 06:00
The problem identified by James Brooks is driving me nuts. There must be a way to stop this from showing up in Fiddler:

Host: v10.vortex-win.data.microsoft.com

HTTP/1.1 408 Request body incomplete
Date: Thu, 08 Mar 2018 16:01:58 GMT
Imported User
Posted on: 20 Feb 2018 06:00
I am also having issues with https://v10.vortex-win.data.microsoft.com/collect/v1 in Fiddler. My filter is on and set to "Show only the following Hosts" -- "localhost" yet I see both localhost and v10.vortex-win.data.microsoft.com  I can right click on it and choose "Filter Now --> Hide v10.vort... yet after a few captures, it starts showing v10 again.  Always with 408 request body incomplete.
Imported User
Posted on: 20 Feb 2018 06:00
Nope, spoke to soon. Adding "Hide if URL contains" did not work. Sorry.
Imported User
Posted on: 20 Feb 2018 06:00
As a side note. Under "Filters" --> "Hide if URL contains" --> v10.vortex-win.data.microsoft.com  does work in hiding it from Fiddler
Eric
Posted on: 19 Feb 2018 06:00
Regarding the claim that "Stealth" doesn't work-- the most likely explanation is that you either wrote the rule incorrectly, or put it in the wrong place. Feel free to email me a SAZ capture demonstrating your issue. bayden at gmail dotcom.
Imported User
Posted on: 06 Feb 2018 06:00
STEALTH doesn't work for me, those requests still show.
Eric
Posted on: 29 Jan 2018 06:00
In the Session's Properties, you can see what exactly the protocol violation in the request is; depending on what the problem is, it reflects either a bug in the client (likely) or something that could be fixed in Fiddler.

To cause a Session to be hidden regardless of protocol errors, you can add the word "STEALTH" to the UI-HIDE value, e.g.

if (oSession.urlContains("watson.telemetry.microsoft.com")) { oSession["ui-hide"] = "STEALTH-boring boring boring...."; }
Imported User
Posted on: 25 Jan 2018 06:00
My host is slightly different: watson.telemetry.microsoft.com.  I tried setting up a "Hide if URL contains" and "hide following hosts", but it still shows up.  I also tried adding a line in the custom rules file, but it still powers through.

It is a protocol violation: "ProtocolViolationInRequest".

Is there a special way I can block this specific request?
Imported User
Posted on: 25 Jan 2018 06:00
By block, I mean hide from the list.
Imported User
Posted on: 16 Jan 2018 05:59
Microsoft telemetry calls to v10.vortex-win.data.microsoft.com bypass the filters and add noise. If my filter says only show localhost, I don't expect to see calls to Microsoft.com.