When your application under test (AUT) uses
BASIC authentication, and you have replayed the default recorded and enhanced
script ( e.g. parameterization, correlation etc. ), it may fail as the authentication process sends the first 401
handshake and fails on the second with an error such as 501.
To check if your application uses BASIC authentication or not, you can of course check with your development team or check in the response header in the vugen replay logs. To resolve this issue and achieve successful replay, you can actually add below function at the very beginning of the action section and then replay your script:
web_set_sockets_option ("INITIAL_BASIC_AUTH", "1");
To check if your application uses BASIC authentication or not, you can of course check with your development team or check in the response header in the vugen replay logs. To resolve this issue and achieve successful replay, you can actually add below function at the very beginning of the action section and then replay your script:
web_set_sockets_option ("INITIAL_BASIC_AUTH", "1");
Performance Testing -You Can'T Improve What You Can'T Measure: How To Ensure Loadrunner Script Replay Sucessfully When Basic Type Of Authentication Used By An Application Under Test? >>>>> Download Now
ReplyDelete>>>>> Download Full
Performance Testing -You Can'T Improve What You Can'T Measure: How To Ensure Loadrunner Script Replay Sucessfully When Basic Type Of Authentication Used By An Application Under Test? >>>>> Download LINK
>>>>> Download Now
Performance Testing -You Can'T Improve What You Can'T Measure: How To Ensure Loadrunner Script Replay Sucessfully When Basic Type Of Authentication Used By An Application Under Test? >>>>> Download Full
>>>>> Download LINK