.Net 6/7 not capturing packets.

[Gary]

I have a library that I'm testing out and the .Net Framework 4.6.2 project logs just fine with the normal app.config values.  When I set up the same project using .Net 6/7 I can't seem to get it to capture any packets.

I run netsh command under an elevated privilege command prompt before starting fiddler and then I run the debug mode in VS 2022 and see no entries come across fiddler.  

C:\WINDOWS\system32>netsh winhttp set proxy 127.0.0.1:8888

Current WinHTTP proxy settings:

    Proxy Server(s) :  127.0.0.1:8888
    Bypass List     :  (none)

The only way I can get it to log anything is to enable "Act as a system proxy on startup".  This isn't too practical as then I'm seeing all traffic, which is a lot.

The request is to an https-enabled site.

Is there something I need to do differently in this case?

All of the articles I have read points to this as the correct direction, but they are all 2019 or older.

 

 

[Nick Iliev]

Hello Gary,

 

You can refer to this documentation article for manual instructions on using Fiddler Everywhere. The only difference from Fiddler Classic is the port used, which is 8866 for Fiddler Everywhere and 8888 for Fiddler Classic. That said, you should be able to explicitly set the proxy through the DefaultProxy property (or its alternative option in the used request library).

As a side note, another option is to try our new Fiddler Everywhere which supports multiple capturing modes including the option to capture traffic from a specific terminal application and its child processes.

 

Regards,
Nick Iliev
Progress Telerik

[Gary]

Thanks for the quick follow-up. The global DefaultProxy solved the problem for my use case.  I'm probably going to refactor our libraries to add an option for proxy so we can selectively turn it on and off as needed.