Proxies in TurboActivate
By default, TurboActivate uses whatever proxies your users have set for their system. Where TurboActivate reads these proxy settings from differs between operating systems:
Windows: The proxy settings are read from Internet Explorer.
Mac OS X: The proxy settings are read from the system internet settings.
Linux / BSD / Solaris: The proxy settings are read from the environment variables
Custom proxy settings
You can overwrite the default system proxy settings both in API and the TurboActivate Wizard. When using custom proxies within TurboActivate they must be in the form Proxy in the form:
Example 1 (just a host):
Example 2 (host and port):
Example 3 (all 3):
Note: If the port is not specified, TurboActivate will default to using port 1080 for proxies.
To override the default system proxies within the TurboActivate API, simply call the
TA_SetCustomProxy() function while passing in the proxy string as a parameter. This sets the custom proxy in memory and all subsequent calls that go through the Internet will use that custom proxy until your process ends.
To clear a previously set custom proxy simply pass in a
Nothingdepending on your programming language).
To bypass the system proxies, and only try to directly connect to the LimeLM servers, pass in an empty string value.
This should go without saying, but if you're specifying a custom proxy you should call
TA_SetCustomProxy() before using any other function (especially ones that require internet connectivity, e.g.
You can pass custom proxy settings to the TurboActivate Wizard using the commandline. For example:
TurboActivate also support NTLM proxies on Windows. To use NTLM proxies you must also specify the domain. For example: