Hi,
Not sure if this helps, but it sounds like the connection is kept open somehow.
If preferences, you can force SoapUI to close connections after each request.
Maybe this will ensure a fresh connection is built without the deleted access token.
Hi,
Not sure if this helps, but it sounds like the connection is kept open somehow.
If preferences, you can force SoapUI to close connections after each request.
Maybe this will ensure a fresh connection is built without the deleted access token.
Wow, that works!. Thanks for the timely help
But i want to understand this functionality. Can you explain this. Since we are setting the preference at a global level, will it affect my other test cases ?
Also i saw the raw-request, and i saw this header parameter "Connection":"Close. By default, since we are using HTTP 1.1, we were seeing "Connection": Keep-Alive. So, if we set a header parameter connection manually, will it over ride the Connection set by ReadyAPI?
Since we are setting the preference at a global level, will it affect my other test cases ? I suppose that depends on exactly what you're testing. My default is close connection. I have some tests where the API demands authentication and others that don't. I suppose those with authentication have to re-authenticate each time instead of "authenticate once and use many". Luckily, it is a global config and if other tests break, then re-enable, which I suppose leads nicely onto your next question.
Also i saw the raw-request, and i saw this header parameter "Connection":"Close. By default, since we are using HTTP 1.1, we were seeing "Connection": Keep-Alive. So, if we set a header parameter connection manually, will it over ride the Connection set by ReadyAPI? Not sure, but that would a be neat little test to try.
Setting the connection header manually, override the default headers. So if anyone wanted to change header for just one request, it is possible
Thanks for the reply, chris
I am going to keep the connection closed for all the api's. Hope it does not affect other api behaviors
