http://blogs.telerik.com/fiddler/posts/13-01-08/capturing-traffic-from-.net-services-with-fiddler gives an example of how to capture traffic from .NET apps. It doesn't work for me.
I am running Sitecore 6.6, a venerable .NET app, in 64 bit mode on IIS on Windows 2008 R2 x64.
I made the recommended changes to the machine.config files in both C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config (this is a 64 bit app, so this one is probably the one in use) and C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config. I know that this has an effect because when I make a mistake to the Framework64's machine.config, I get a 503 error.
Anyway, I have a feature in Sitecore that reaches out to another server via HTTPS (SharePoint Integration Framework, aka SPIF). Fiddler does not catch this. All Fiddler catches is traffic generated by my (user mode) web browser.
If .NET application traffic was being routed through a proxy, then the Sitecore SPIF feature that reaches out to the other server would fail.
Oh, I know that Sitecore SPIF is indeed reaching out because Wireshark shows the traffic.
If Fiddler captures .NET application HTTP traffic, why is it not doing it here?
I am running Sitecore 6.6, a venerable .NET app, in 64 bit mode on IIS on Windows 2008 R2 x64.
I made the recommended changes to the machine.config files in both C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config (this is a 64 bit app, so this one is probably the one in use) and C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config. I know that this has an effect because when I make a mistake to the Framework64's machine.config, I get a 503 error.
Anyway, I have a feature in Sitecore that reaches out to another server via HTTPS (SharePoint Integration Framework, aka SPIF). Fiddler does not catch this. All Fiddler catches is traffic generated by my (user mode) web browser.
If .NET application traffic was being routed through a proxy, then the Sitecore SPIF feature that reaches out to the other server would fail.
Oh, I know that Sitecore SPIF is indeed reaching out because Wireshark shows the traffic.
If Fiddler captures .NET application HTTP traffic, why is it not doing it here?