03-08-2013, 10:58 PM
Using API v 2.10 plr element (packet lost rate) is empty in the output.
Based on that it can't be parsed as number.
Is it a bug, or it has to be enabled somehow in reguest? I can specify how the plr should be using custom connectivity profile. But it has no efect on plr at the output.
Here is output example produced by v.2.9
and here same example produced by v. 2.10
Thanks
Pospa
Based on that it can't be parsed as number.
Is it a bug, or it has to be enabled somehow in reguest? I can specify how the plr should be using custom connectivity profile. But it has no efect on plr at the output.
Here is output example produced by v.2.9
Code:
<response>
<statusCode>200</statusCode>
<statusText>Ok</statusText>
<data>
<testId>130129_CK_G</testId>
<summary>http://10.0.2.221/results.php?test=130129_CK_G</summary>
<testUrl>http://www.google.com/</testUrl>
<location>IE</location>
<connectivity>DSL</connectivity>
<bwDown>1500</bwDown>
<bwUp>384</bwUp>
<latency>50</latency>
<plr>0</plr>
<completed>Tue, 29 Jan 2013 14:38:04 +0000</completed>
<runs>3</runs>
<successfulFVRuns>3</successfulFVRuns>
<successfulRVRuns>3</successfulRVRuns>
<average>
and here same example produced by v. 2.10
Code:
<response>
<statusCode>200</statusCode>
<statusText>Ok</statusText>
<data>
<testId>130308_PF_C</testId>
<summary>http://176.74.165.231/results.php?test=130308_PF_C</summary>
<testUrl>http://www.google.cz/</testUrl>
<location>IE</location>
<connectivity>DSL</connectivity>
<bwDown>0</bwDown>
<bwUp>0</bwUp>
<latency>0</latency>
<plr></plr>
<completed>Fri, 08 Mar 2013 12:48:54 +0000</completed>
<testerDNS>8.8.8.8,8.8.4.4</testerDNS>
<runs>1</runs>
<successfulFVRuns>1</successfulFVRuns>
<successfulRVRuns>1</successfulRVRuns>
<average>
Pospa