Need More Info
Last Updated: 31 Aug 2020 06:11 by ADMIN
Mark DeMichele
Created on: 04 Aug 2020 11:39
Type: Bug Report
1
Fiddler refusing to ignore teams.microsoft.com and is causing my MS Teams app on windows to break

I recently am having an issue with MS Teams while running fiddler.  MS Teams keeps giving disconnect errors. That's when I noticed that fiddler it proxying it's traffic even though I have filters set to "Show only the following Hosts", and teams.microsoft.com are not included in the hosts.  I also notice other items in my sessions list that are not in my list of hosts so what is going on?

I don't really want to post my list of hosts publicly.  If you need them, please let me know and maybe I can email them to someone.

 

10 comments
ADMIN
Nick Iliev
Posted on: 31 Aug 2020 06:11

Hi Mark,

 

Using the exact same version for Fiddler and adding the enlisted hosts in the skip decryption section of HTTPS tab stopped showing the requests that were made to these hosts (they are just not shown but still being captured underneath) - the MS Teams is working as expected with no issues but notice that I am explicitly stopping the capturing before closing Fiddler.. Regarding the format of the bypass list, refer to the comment that Eric made here.

 

Regards,
Nick Iliev
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Mark DeMichele
Posted on: 25 Aug 2020 19:02

Here's some more info.

MS Teams Version: 1.3.00.21759

Fiddler Version: v5.0.20202.18177 5.0.20202.18177 for .NET 4.6.1

On the HTTPS tab in Options I added this.

*.microsoft.com
*.live.com
*.office.net
*.office365.com
*.office.com

On the connections tab under Bypass Filler for URL that start with:  I originally had something similar but when it wasn't working I moved those similar settings to the HTTP tab.  Now, I just have this for Bypass.

<-loopback>;

Should I try to add them there.  I thought having the HTTPs one would be enough, but it's still giving me trouble.  If I do add items to the Bypass part, what format do I use.  That "starts with.." statement seems a little misleading.

Thanks for your help.

Eric
Posted on: 25 Aug 2020 15:39

For what it's worth, changes to the proxy bypass list are applied the next time Fiddler capturing is enabled, so you can just hit F12 twice on Fiddler's main screen to detach Fiddler, then reattach with the new bypass list.

 

ADMIN
Garo
Posted on: 25 Aug 2020 13:47

Hello Mark,

I'm having difficulties with reproducing the reported issue when using Fiddler with Microsoft Teams. In the past, I've had occasions where Outlook would misbehave when Fiddler is running, but this was always resolved by adding the outlook URLs to the bypass list. Also, you are correct that modifying the bypass list requires you to restart Fiddler to take effect.

We attempted to reproduce the issue with different versions of Fiddler and version 1.3.00.19173 of Teams, but without success. Can you tell me which version of Fiddler and Teams are you using? Also, have you tried reinstalling Fiddler? 

Regards,
Garo
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Mark DeMichele
Posted on: 18 Aug 2020 22:37
I'm still having issues with this. When I fiddler is running MS Team gives a "disconnected" error.   However, it seems to work except for showing me updated status of people.  As soon as I stop capturing or close fiddler, the errors fix themselves.
Eric
Posted on: 06 Aug 2020 13:46

The "Show only" is literally a display-only filter; it doesn't change what is captured.

Running Teams though Fiddler ought to work just fine, but if you don't care about Teams' traffic, your best bet is to use Tools > Options > HTTPS and either change the dropdown so that Fiddler only decrypts HTTPS traffic from browsers OR update the box at the bottom so Fiddler skips decryption for the hostnames used by Teams.

Mark DeMichele
Posted on: 05 Aug 2020 14:47
My previous change to bypass the urls may actually  be working.  I think I needed to restart fiddler.  I'll let you know if teams breaks again.
Mark DeMichele
Posted on: 05 Aug 2020 14:47
BTW, this just recently started happening in the last few weeks.  I'm not sure if I updated fiddler within that time.  But something has changed not too recently to cause this.
Mark DeMichele
Posted on: 05 Aug 2020 14:45

So I did discover why I was seeing "yellow" entries for teams.microsoft.com.  I believe it was due to the setting

"If protocol violations are observed: Warn on all errors" setting.  I changed that to "Do nothing" and now I don't see those guys in the list of sessions.  However, that still did not fix MS Teams from losing connection.

I went to the SO link you gave and the last post suggested to add to the list of Bypass Fiddler for URLS that start with....

I modified it to do this,

<-loopback>; *office.com; *office365.com; *live.com;*.microsoft.com;

But that didn't help.  I'll look for other solutions now.

ADMIN
Nick Iliev
Posted on: 05 Aug 2020 11:24

Hello Mark,

 

Indeed Fidler will capture traffic from multiple processes. You could limit that by using one of the solutions suggested here. However, notice that some of the Microsoft products like Teams, Outlook, Office365 are tending to have issues when they have to change the proxy settings dynamically (without explicit restart). This is the very same reason why Fiddler is capturing traffic from those products even if the capturing is turned off (they are still using the old proxy settings). In some cases, those products will start experiencing network issues as they are not changing the proxy setting even when Fiddler has been stopped and capturing is off. In such cases, restarting the Microsoft product in question is one of the viable solutions.

 

Regards,
Nick Iliev
Progress Telerik