We have had clients need to specify an HTTP proxy server that our various Desktop add-ons and applications need to use when communicating with some external HTTPS resources. For example when using RemoteLaunch, the DesktopDataSync or Jira Configuration Helper tools. This article explains the process for listing a proxy server.
When connecting RemoteLaunch to an instance of SpiraTest or SpiraTeam that is externally hosted you may have an issue where RemoteLaunch does not know to use a local proxy server. This articles describes an easy solution to modify RemoteLaunch to use your current Internet Explorer (IE) proxy settings.
This article is now obsolete.The fix has been applied to resolve the proxy server information in newer versions of Remote Launch.
In situations where your SpiraTest, SpiraPlan or SpiraTeam server is located on a company network that does not have direct Internet access (and connects through a proxy server), some of the integration features of Spira may not work correctly:
This article outlines the step necessary to tell the Spira server to use the proxy server for its Internet connections.
Article can be considered as obsolete.Described fix applies to outdated versions of the application only.