A frequent scenario in corporate networks is the necessity to use a proxy to send HTTP requests "outside" (e.g. to our license server), but not to use that proxy for internal traffic. This scenario was especially a problem for CloudTest Lite users in prior releases.
In order to get beyond it, the user had to choose between either:
- (a) Turning on the proxy setting, and losing the ability to run behind-the-firewall Compositions (because the proxy may not handle behind-the-firewall traffic)
- (b) Turning off the proxy setting, and breaking license checks (thus preventing you from playing any Compositions anyway!).
Users can utilize theHTTPProxy.BypassList service setting to define a bypass proxy list. A list of hosts can be entered using commas to separate one host from another.
This feature works differently in CloudTest Lite and Pro.
- In CloudTest Pro, Maestro has its own proxy settings that are not used by anything else. So, the user can configure how Composition traffic will be sent, without affecting anything else. Conversely, when configuring a proxy for license checks, it won't affect Maestro, because again, the settings are separate.
Maestro Service Settings are found in Central > Servers > Settings (lower panel).
- In CloudTest Lite, however, there are only the "global" settings that are used for both license checks and Maestro.
Therefore, in Lite, the bypass proxy list—which is found in Central > Site Administration (shown above)--permits users to specify the proxy for some servers (e.g. "cloudtestmanager.soasta.com"), but not for others (e.g. "internal-server.local"). The Bypass proxy list server setting can be overridden at the target level via system property overrides.