Case Status
Log In


  • RSS Feed

Last modified on 12/1/2022 11:52 AM by User.



Configure .NET Applications

To allow the .NET Framework to automatically connect to Fiddler, start Fiddler Classic before starting the .NET application.

To temporarily connect a .NET application to Fiddler Classic, use the GlobalProxySelection class to set a proxy:

System.Net.WebRequest.DefaultWebProxy = new System.Net.WebProxy("", 8888);

Or, specify a proxy inside the yourappname.exe.config file.

for VS2019+ a config can be found in <project>\.vs\<projectname>\config

  • If the .NET application is running in your current user account, add the following content inside the configuration section:

       <proxy bypassonlocal="false" usesystemdefault="true" />

See MSDN for more on this topic.

  • If the .NET application is running in a different user account (for example, a Windows service), edit the machine.config file:

    <!-- The following section is to force use of Fiddler Classic for all applications, including those running in service accounts -->  <>
      <proxy autoDetect="false" bypassonlocal="false" proxyaddress="" usesystemdefault="false" />

Or, manually specify the proxy on an individual WebRequest object:

    objRequest = (HttpWebRequest)WebRequest.Create(url);
    objRequest.Proxy= new WebProxy("", 8888);

Note: Important: Regardless of other settings, .NET will always bypass the Fiddler Classic proxy for URLs containing localhost. So, rather than using localhost, change your code to refer to the machine name. For instance:

  • This URL will not appear in Fiddler:


  • This URL will appear in Fiddler:


Configure .NET Core Applications

Setup the proxy via netsh tool in commmand line the following way

see Netsh Docs for more info on this topic

    netsh winhttp set proxy

To remove the proxy use the following

    netsh winhttp reset proxy