In order to circumvent that, we use web_get_int_property API to retrieve the file size.  This file size will then be used to make comparison with the actual known file size on the server.  For usage of web_get_int_property, you can refer to the Function Reference available in Vugen.

On a brief overview, place the web_get_int_property APT after the request (web_url, web_custom_request, etc.) made for the file (PDF/excel).  I’ve extracted examples from LoadRunner Yahoo Groups and list them below for your convenience.

Example 1:

lr_message(“%ld”,web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE));

web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE);

web_get_int_property(HTTP_INFO_DOWNLOAD_TIME);

Note, HTTP_INFO_DOWNLOAD_SIZE does not give the actual size of PDF file.  This HTTP_INFO_DOWNLOAD_SIZE gets the body bytes, header bytes, and chunk bytes.  Therefore, you may need to fine tune the script to determine a range value of the PDF file size due to the header and chunk bytes.

Example 2:

float fFileDownloadSize, fFileDownloadTime, fFileDownloadRate;

funcFileDownload()
{
fFileDownloadSize = (web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE)/1024.);
//in kilobytes
fFileDownloadTime = (web_get_int_property(HTTP_INFO_DOWNLOAD_TIME)/1000.);
//in seconds
fFileDownloadRate = fFileDownloadSize/fFileDownloadTime; //in KB/s

lr_output_message(“Size of download was %.0f kilobytes; Time of download was %.3f seconds”, FileDownloadSize, fFileDownloadTime);

lr_output_message(“Rate of download was %.2f KB/sec”, fFileDownloadRate);

return 0;
}

Example 3:

long DSize=0;

float DTime=0;

DSize = web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE);

lr_output_message(“DSize is: %.2ld Bytes”, DSize);

lr_output_message(“File Download size is: %.2ld KB”, DSize /1024);

DTime = web_get_int_property(HTTP_INFO_DOWNLOAD_TIME);

lr_output_message(“File Download Time is:%.2f Seconds”, DTime / 1000);

web_reg_save_param(“p_EmpID”,
“LB=Emp_ID=”,
“RB=\”",
“Ord=ALL”,
“RelFrameId=1″,
“Search=Body”,
“IgnoreRedirections=Yes”,
LAST);

This is familiar coding where p_EmpID will be captured with LB of EMP_ID= and RB of “.  However, another parameter to note in web_reg_save_param is the ORD, or Ordinal.  This specifies the locaiton of the value to capture if multiple occurrences of LB and RB exists.  By default, the value is ORD=ALL which meant that all occurrences will be captured.  When all occurances are captured, they are stored in an array.  The total number of values captured can be accessed by placing a _count suffix after the parameter name.  Example (note, Total_Employees have to be defined as an integer in the script):

Total_Employees=atoi(atoi(lr_eval_string(“{p_EmpID_count}”­));

While to access a specified value in the array, you will put an index after the parameter in _{index} format.  Example illustrates reading the 2nd Employee ID in the array:

Current_EmployeeID=atoi(lr_eval_string(“{p_Emp_ID_2}”­));

Of course, these are just methods to read the values extracted for your scripting work.  Hopefully, you will find it easier when you are performing scripting work.

NOTE (21 Oct 2008):  Corrections to the default value of the Ordinal parameter.  It should be ORD=1, meaning the first occurence, instead of ORD=ALL.