Support forum
wyDay blog
wyDay Home

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:

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: http://username:password@host:port/

Note: If the port is not specified, TurboActivate will default to using port 1080 for proxies.

TurboActivate API

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.

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. TA_IsGenuine(), TA_Activate(), etc.)

TurboActivate Wizard

You can pass custom proxy settings to the TurboActivate Wizard using the commandline. For example:

TurboActivate.exe --proxy="http://username:password@host:port/"

NTLM Proxies

TurboActivate, the TurboFloat library, and the TurboFloat Server all support NTLM proxies on Windows. To use NTLM proxies you must also specify the domain. For example: