Many of the DataDirect for ODBC drivers use the HTTPS protocol to communicate with the data source or other required systems. For instance, cloud-based data sources use HTTPS as the primary communication protocol between a driver and the data source. Additionally, some on-premises data sources may use HTTPS for certain features, even though they primarily use TCP-based protocol to communicate between the driver and data source. SQL Server, for example, primarily employs a TCP-based wire protocol, but uses HTTPS to fetch encryption keys used by the Transparent data encryption feature from SQL Server Azure.

In many cases, transparent proxies are used to allow the driver to connect to the data source or system using HTTPS. However, secure data centers often require any communication external to the data center to be routed to a dedicated HTTP proxy. The DataDirect ODBC drivers provide the following options to allow the driver to route HTTPS requests to the specified HTTP proxy:

  • Proxy Host (ProxyHost)

  • Proxy Port (ProxyPort)

  • Proxy User (ProxyUser)

  • Proxy Password (ProxyPassword)

For additional information on configuring HTTP proxies, refer to the user's guide for your driver.