question

Upvotes
Accepted
0 2 1 5

Real-Time SDK (RRTO) libcurl issue connecting to a proxy server

We are connecting successfully to our proxy server (https://) using our own version of libcurl (statically built) when requesting data from the Refinitiv Datastream web-service

We also use RRTO for real-time market data, though their is an issue where the RT SDK (which uses libcurl 7.78) fails to connect to our proxy server, because we use https, as opposed to http as the address. If we use http:// as the proxy address it works fine

The libcurl.dll comes shipped with the RT SDK

The error returned from the SDK is:

'Failed to send a request to the token service. Text: Error: Failed to perform the request with text: A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision.'

Now we are using the standard service discovery code as documented online

The ChannelType is set to RSSL_ENCRYPTED (1) and the EncryptedProtocolType is set to RSSL_SOCKET (0).

The proxy details are set when doing serviceDiscovery.registerClient()

We have the OpenSSL 1.0 DLLs in place

Also without going through a proxy all works fine. It's just the http(s) that is the issue.

Does anyone do a similar thing using the RT SDK?

eta-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
47.2k 110 44 60

@manjinder.singh

I think that the libcurl.dll shipped with the RTSDK doesn't support this HTTPS-PROXY feature.

I got the same error when using it with the HTTPS protocol.

Error: Failed to perform the request with text: A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision.'. ', ErrorCode='-1'

You may try to build libcurl on Windows to make it support this feature.

Otherwise, you may try to use libcurl.dll from this website.

I am unable to test it because I don't have an HTTPS proxy server.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.