Pending Review
Last Updated: 08 Nov 2019 14:25 by Elroid
Elroid
Created on: 07 Nov 2019 14:53
Type: Bug Report
0
oSession.SaveResponseBody sometimes saves json as readable text, sometimes as garbled unreadable mishmash.

Run 1 Example 1 (first 32 characters): {"SummaryTracker":null,"Column1

Run 2 Example 2 (first 32 characters):  ¢ €ªªªêÿteÐ(È„´47ó ¯*·:˜y@X

CustomRules.js

if (oSession.uriContains("/yadayada?Id=")) 
{
var qs = oSession.fullUrl.ToString;
var qsT = oSession.fullUrl.Split("=");
var qsone = qsT[1] + "_ABC";
oSession.SaveResponseBody("C:\\temp\\" + qsone + ".json");
}

Using latest Chrome as browser. Running fine for many months until 1 November 2019, Boom! Can anyone tell me what is going on? It appears to be random.

Thanks!

1 comment
Elroid
Posted on: 08 Nov 2019 14:25
Data appears to show up correctly when viewing sessions in saved SAZ file. It is just not saving to file correctly in random instances.