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
In 4.5.2, session cookies don't persist across different types of calls.
Call 1: HTTP POST
response: set-cookie
Call 2: AMF POST
request: no cookie present
Call 3: HTTP GET
request: cookie is present
The cookie should be set after call 1, but it's not present in call #2. It is present in call #3. This used to work in 3.5.1. HTTP session is checked, AMF session is not checked.
Call 1: HTTP POST
response: set-cookie
Call 2: AMF POST
request: no cookie present
Call 3: HTTP GET
request: cookie is present
The cookie should be set after call 1, but it's not present in call #2. It is present in call #3. This used to work in 3.5.1. HTTP session is checked, AMF session is not checked.
