Session/Cookie handling bug in soapUI 4.5.1
I'm trying to upgrade to soapUI 4.5.1 but I'm running in to problems concerning the handling of Cookies. All test cases use the "Maintain HTTP session" setting since we rely in part on using the JSESS...
Forum Discussion
I have been experiencing this same issue as described by mannyvel. I had a perfectly working test two days ago, which maintained session through Cookie: JSESSIONID=XXXXX, but today, presumably after the latest nightly build, it is no longer adding the JSESSIONID cookie http header to subsequent requests.
Is there a way for me to roll back to an earlier build? And are there any plans to fix this? I have an important project pending in the next couple of days and would really hate to have to resort to manual groovy scripting.
Thank you.l
Is there a way for me to roll back to an earlier build? And are there any plans to fix this? I have an important project pending in the next couple of days and would really hate to have to resort to manual groovy scripting.
Thank you.l
