http 400 bad request is showing up in the test execution in controller at the very exact time while running the script with the settings.
simulate a new user - off
clearcache - off
ihs shows "request failed: error reading the headers"
If i run the same scenario with the below settings then there is no http 400 bad request error or request failed: error reading the headers in the log.
simulate a new user - on
clear cache - on
why this error shows if i use the same user and not for the new users.
note: there is nothing to correlate. the jsession id is taken care of LR.
1. LR 9.5
4. - Concurrent groups,
6. New recording
7. Permanent http/html 5000
9. Windows-XP, SP2
10. Not filed
What happens when you run multiple iterations in Vugen using the differing settings that you list?
Unless you are writing a compiler, strtok is NOT the answer.
QAF is still an exercise in self-sufficiency! (Thank JB!)
thanks. i ran it in vugen and it looks like the cookie is grwowing huge and hence the http 400 header error at http server. dev is investigating why the cookie is growing.