Websocket API didn't receive response after Service Discovery Call

elektron
elektron Newcomer
in Refinitiv Data Platform

Hello!

We succesfully received token via https://api.refinitiv.com:443/auth/oauth2/v1/token

and then we are trying to call https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket.

But this https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket does not return anything.

One day ago, the request https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket correctly returned a list of endpoints.

If i try to call https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket via browser it return

code"401"message"Authorization header is missing"status"Unauthorized"

so we has an network access.

What it can be?

Tagged:

Best Answer

  • umer.nalla
    umer.nalla LSEG
    Answer ✓

    Hi @elektron

    Are you using C#?

    If so, there is an issue due to the increase in the number of services added over the weekend, the response has started being chunked.

    As a result of this, if you are using the C# example or another scenario where you are checking the service discovery response content length - this would now return -1 and something like the following would now fail:

    if (webResponse.ContentLength > 0)

    so the above should be replaced with something like:

    if (webResponse.GetResponseHeader("Transfer-Encoding").Equals("chunked") || webResponse.ContentLength > 0)

    Hope this helps.

    If you were using our C# service discovery example on Github, these will be updated shortly.


Answers

Categories