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
Note that in 4.5.1, cookie information is occasionally not sent. Here are the headers from one login attempt:
Request
-------
POST /MYAPP/j_spring_security_check?j_username=testuser1&j_password=testpassword&submit=login HTTP/1.1
Accept-Encoding gzip,deflate
Content-Type application/xml
Content-Length 0
Host 54.236.95.134:8085
User-Agent Apache-HttpClient/4.1.1 (java 1.5)
Response
--------
HTTP/1.1 302 Found
Set-Cookie: JSESSIONID=E85FAE1859332A53F04E6B254B728219; Path=/MYAPP
Location: http://MYIP:MY_PORT/MYAPP/;jsessionid=E ... 254B728219
Content-Length: 0
Date: Tue, 16 Apr 2013 18:51:55 GMT
Server: MY Server
Request
-------
POST /MYAPP/messagebroker/amf HTTP/1.1
Content-Length 80
Host MYIP:MYPORT
User-Agent Apache-HttpClient/4.1.1 (java 1.5)
The request should look like this (from a successful server interaction):
POST /MYAPP/messagebroker/amf HTTP/1.1
Content-Length: 80
Host: MYIP:MYPORT
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Cookie: JSESSIONID=DBCE025C4B47D9B8402FF2857585405F
Cookie2: $Version=1
This only happens when running > 1 client. I downloaded the latest soapui nightly build (16 apr 2013), and cookie functionality is totally broken. This is sort of basic - how solid is the cookie/session handling in the Pro version?
Request
-------
POST /MYAPP/j_spring_security_check?j_username=testuser1&j_password=testpassword&submit=login HTTP/1.1
Accept-Encoding gzip,deflate
Content-Type application/xml
Content-Length 0
Host 54.236.95.134:8085
User-Agent Apache-HttpClient/4.1.1 (java 1.5)
Response
--------
HTTP/1.1 302 Found
Set-Cookie: JSESSIONID=E85FAE1859332A53F04E6B254B728219; Path=/MYAPP
Location: http://MYIP:MY_PORT/MYAPP/;jsessionid=E ... 254B728219
Content-Length: 0
Date: Tue, 16 Apr 2013 18:51:55 GMT
Server: MY Server
Request
-------
POST /MYAPP/messagebroker/amf HTTP/1.1
Content-Length 80
Host MYIP:MYPORT
User-Agent Apache-HttpClient/4.1.1 (java 1.5)
The request should look like this (from a successful server interaction):
POST /MYAPP/messagebroker/amf HTTP/1.1
Content-Length: 80
Host: MYIP:MYPORT
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Cookie: JSESSIONID=DBCE025C4B47D9B8402FF2857585405F
Cookie2: $Version=1
This only happens when running > 1 client. I downloaded the latest soapui nightly build (16 apr 2013), and cookie functionality is totally broken. This is sort of basic - how solid is the cookie/session handling in the Pro version?
