Overview
Inflectra has several add-ons and downloads for integrating other tools or assisting with configuration and maintenance tasks. These applications often have to access external web resources over HTTPS (e.g. third-party APIs) to perform their tasks. In most cases the application will automatically detect the local IT network settings and any proxy servers, and know how to route to the requested resources. In some cases however, you may be required to explicitly specify which proxy server to use.
For these cases, we explain how to modify the application's configuration file to specify the proxy server. You can configure a .NET Framework application to use a proxy server for HTTP communication by adding a
system.net section to its configuration file. We will describe how to do this step by step.
Solution
First, you need to locate the installation location of the application you are working with. For example, if you are using RemoteLaunch, it would be:

From here, you should open up the <application>.config file into a text editor:
<?xml version="1.0"?>
<configuration>
...
</configuration>
Option 1: Using the Default Proxy
You now need to add the following:
<configuration>
<system.net>
<defaultProxy enabled="true" useDefaultCredentials="true">
</defaultProxy>
</system.net>
</configuration>
If that works you are all set. If that doesn't work, then proceed to Option 2 below.
Option 2: Using a Custom Proxy
To enter a custom proxy, you now need to add the following:
<configuration>
<system.net>
<defaultProxy enabled="true" useDefaultCredentials="false">
<proxy
proxyaddress="http://yourproxyaddress:port"
bypassonlocal="true"
autoDetect="false"
/>
<!-- Optional: Add a bypass list if needed -->
<!--
<bypasslist>
<add address="[0-9a-zA-Z]+\.example\.com$" />
</bypasslist>
-->
</defaultProxy>
</system.net>
</configuration>
where you enter the following:
- proxyaddress: the URL of your proxy server
- bypassonlocal: set this to true
- autoDetect: set this to false