Hi,
Were you able to find a workaround for this? I've come across the same issue (SOAP UI 3.6.1 on WinXP) and it's causing an error on the second invocation (because the endpoint expects POST data, not a GET request, see attached, screenshot from Wireshark). Headers etc are like yours (user agent "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko" and so on), except the second invocation is always a GET. In my case the second invocation returns an error, which is fine because SOAP UI is still "looking" for a response from the POST (which succeeds). However, when I do a burst of 5 simultaneous calls (in a TestSuite where each TestCase calls the same endpoint), SOAP UI will arbitrarily "see" the response from the (failed) GET as the response to the POST and report an error.
Any help would be much appreciated.
Lorkus
