Invalid response issue

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.

@sd

I found the code in Async Key Mechanisms in Managing Active/In-Flight Jobs section.

var job = extractionsContext.ExtractWithNotesStart(extractionRequest);
var handle = job.ToString();

job = AsyncJob<ExtractionResult>.Parse(handle);
job = extractionsContext.MonitorJob(job);

From this code, we can change the job to string, modify the string, and then parse it back to the job.

Therefore, I have created a function to change HTTP to HTTPS.

static IAsyncJob<RawExtractionResult> FixProtocol(ref IAsyncJob<RawExtractionResult> result)
{           
    var handle = result.ToString();
    Console.WriteLine("handle: {0}", handle);
    if (handle.Contains("http://"))
    {
        handle = handle.Replace("http://", "https://");
        Console.WriteLine("new handle: {0}", handle);
    }
  return AsyncJob<RawExtractionResult>.Parse(handle);          
}

I have applied it to the following code:

//AsyncJob is in this namespace
using ThomsonReuters.Dss.Api.Core.HttpOData;
...
...
RawExtractionResult extractionResult = null;
IAsyncJob<RawExtractionResult> resultTask = null;

resultTask = extractionsContext.ExtractRawStart(extractionRequest);
do
{
    resultTask = extractionsContext.MonitorJob<RawExtractionResult>(FixProtocol(ref resultTask)); 
    if (resultTask.Status == ThomsonReuters.Dss.Api.Jobs.JobStatus.InProgress)
    {
        System.Threading.Thread.Sleep(2000);
    }
} while (resultTask.Status != ThomsonReuters.Dss.Api.Jobs.JobStatus.Completed);

extractionResult = resultTask.Result;

DssStreamResponse streamResponse = extractionsContext.GetReadStream(extractionResult);

Following the reply given by jirapongse.phuriphanvichai here's the code that I had to add to fix the issue. Hope this helps any one

 IEnumerable<ExtractionRow> Extract(ExtractionRequestBase extractionRequest)
        {
            ExtractionResult extractionResult = null;
            IAsyncJob<ExtractionResult> resultTask = null;


            resultTask = extractionsContext.ExtractWithNotesStart(extractionRequest);


            do
            {
                if (resultTask.MonitorUri.Scheme .Equals("http", StringComparison.InvariantCultureIgnoreCase))
                    resultTask = FixProtocol(resultTask);

                resultTask = extractionsContext.MonitorJob(resultTask);


                if (resultTask.Status == Dss.Api.Jobs.JobStatus.InProgress)
                {
                    System.Threading.Thread.Sleep(5000);
                }


            } while (resultTask.Status != Dss.Api.Jobs.JobStatus.Completed);


            extractionResult = resultTask.Result;


            return extractionResult.Contents;
        }


        static IAsyncJob<ExtractionResult> FixProtocol(IAsyncJob<ExtractionResult> result)
        {
            var handle = result.ToString();


            handle = handle.Replace("http://", "https://");


            return AsyncJob<ExtractionResult>.Parse(handle);
        }

I would refrain from mutating a job handle and simply create a new AsyncJob:

public static IAsyncJob<TResult> ChangeMonitorUrlToUseHttps<TResult>(this IAsyncJob<TResult> job)
{
    var url = job.MonitorUri;
    if (url.Scheme == "https")
        return job;

    var urlBuilder = new UriBuilder(url) {Scheme = "https"};
    var newJob = new AsyncJob<TResult>(urlBuilder.Uri, job.Status, job.Progress, job.Result);
    return newJob;
}