TRTH returns http

out.txtIn my intraday summary request, I can easily replicate the issue, almost one out of five.

1) request token

2) request https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw

requestheader, requestbody are hardcoded and are definitely correct. It has no issue to return 202 status code.

3) I then extract new url by res.headers["location"] and sometimes it gives me http://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x05d230d513ab3036')

whenever it has http protocol, the next request always returns 200 but of course you are not able to get its text. I also attached a file that is the print out of response object.

Find more posts tagged with

tick-history-rest-api

Accepted answers

moragodkrit.chumsri_1

@jim.yu

This seems to be TRTH issue mentioned in

https://community.developers.refinitiv.com/questions/16886/invalid-response-issue.html

The workaround for now is to use string function to replace HTTP with HTTPS.

Below is information provided by Christiaan.

The servers have an intermittent issue with the location URLs returned in the 202 response. It is sometimes returned as HTTP instead of HTTPS. Using a location with HTTP will fail.
Note: the issue does not depend on the type of data request you make.
The current workaround is that you monitor the returned URLs and “add the s” to get consistent performance. A solution for the underlying problem is expected in the 11.2 release in September.
Please accept our apologies for the inconvenience.

All comments