We are getting TLS1.1 not supported error while using .NET Framework 4.8 and DataScope.Select.Res...

prasad.reddy01

...tApi.Client 17.2.129.0. It seems that we only got the errors when using "x-direct-download" in the request header. Could you please advise?

client is claiming when they run custom extractions and downloading the output file with S3 direct header they are getting below error:

We got TLS errors frequently today (maybe since last week). We had to retry several times to get the files downloaded, and this caused delays.

Take file DAILY-1MIN-EURO2-20230825.csv.gz for example. The file id is 0x0899d721a3e90bfd. Error logs (including RequestId) like below:

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidTlsVersion</Code><Message>Amazon S3 will stop supporting TLS 1.0 and TLS 1.1 connections. Please update your client to use TLS version 1.2 or above. To learn more and to update your client, see https://go.aws/3AUlVSb. For further assistance, contact AWS support.</Message><RequestId>JKXGNP0M3VQGQX13</RequestId><HostId>XBQEirTiGjLByJz42qN4hHq35v6bL4xAjgFAZRzav7W/GzTIN8j0xZS4Jj9HaEy2pTHM/YhFeZU=</HostId></Error> :
at DataScope.Select.Api.Core.HttpOData.Http.HttpClientExceptionDecorator+<ParseResponseError>d__1b.MoveNext () [0x0057a] in <f747139363544b3990dfff486c66c322>:0

Could you please confirm the TLS version that MLP sent to Refinitiv side?

If MLP sent TLS1.2 or TLS1.3, could you please check further why it became TLS1.1 on Refinitiv side?

If MLP sent TLS1.1, could you please advise how to specify TLS version in DataScope.Select.RestApi.Client (version 17.2, with .NET Framework 4.8)?

Btw, according to our logs, the TLS error was not consistent, it’s usually gone after retried several times. So I suspect the issue is on some of your load-balance servers.

Jirapongse

@prasad.reddy01

Thank you for reaching out to us.

I ran the RTH Tutorial 5 example code to replicate this issue. However, I can run it properly on Windows 10, and Visual Studio 2019 (.NET Framework 4.8). I can download a file from AWS properly. Therefore, please run the RTH Tutorial 5 example code and let us know the result.

Otherwise, you can try the following code to set the TLS version to 1.2.

            System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
            DssClient dssClient = new DssClient();

You can also enable tracing in the .NET Framework by adding the following configurations into the app.config file.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>
    </startup>
    <system.diagnostics>
        <trace autoflush="true"/>
        <sources>
            <source name="System.Net" maxdatasize="1024">
                <listeners>
                    <add name="TraceFile"/>
                </listeners>
            </source>
            <source name="System.Net.Sockets" maxdatasize="1024">
                <listeners>
                    <add name="TraceFile"/>
                </listeners>
            </source>
        </sources>
        <sharedListeners>
            <add name="TraceFile" type="System.Diagnostics.TextWriterTraceListener" initializeData="trace.log"/>
        </sharedListeners>
        <switches>
            <add name="System.Net" value="Verbose"/>
            <add name="System.Net.Sockets" value="Verbose"/>
        </switches>
    </system.diagnostics>
  <runtime>
....

The trace.log file will be created in the current working directory.