Double requests?
Hi, I'm new to SoapUI, but can't imagine that this would be the expected behaviour;
In SoapUI 3.6.1, I created a new HTTP testcase. It does a POST request to a server. I initially had trouble with the line endings in the request content having only \n, it has to be \r\n. So, I googled it, and saw that I could add ${="\r"} (groovy stuff?) to the end of each line.
So I did, and this seems to work just fine in SoapUI. It sends the request and shows the response from the server. However - when I sniff the traffic with Wireshark, it shows that two requests are sent(!). The first one works as I wanted, but the second one sends ${="\r"} at the end of each line, over the wire (without expanding it to carriage return). And this is not what the server expects, of course.
Also, the first request has "UserAgent: Jakarta Commons-HttpClient/3.1" and the second request (the weird one) has "UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko)".
I'm imagining that adding the groovy:ish carriage return code triggers something, making SoapUI send double requests? One in "groovy mode", where \r is expanded, and one in "normal mode" where ${="\r"} are sent literally.. But I'm guessing.
Unfortunately my employer has 3.6.1 as "the certified version" of SoapUI, so trying a newer version is not a simple task for me. Can anyone confirm this, or explain to me what I'm doing wrong? :-)
Thanks in advance,
Stefan
In SoapUI 3.6.1, I created a new HTTP testcase. It does a POST request to a server. I initially had trouble with the line endings in the request content having only \n, it has to be \r\n. So, I googled it, and saw that I could add ${="\r"} (groovy stuff?) to the end of each line.
So I did, and this seems to work just fine in SoapUI. It sends the request and shows the response from the server. However - when I sniff the traffic with Wireshark, it shows that two requests are sent(!). The first one works as I wanted, but the second one sends ${="\r"} at the end of each line, over the wire (without expanding it to carriage return). And this is not what the server expects, of course.
Also, the first request has "UserAgent: Jakarta Commons-HttpClient/3.1" and the second request (the weird one) has "UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko)".
I'm imagining that adding the groovy:ish carriage return code triggers something, making SoapUI send double requests? One in "groovy mode", where \r is expanded, and one in "normal mode" where ${="\r"} are sent literally.. But I'm guessing.
Unfortunately my employer has 3.6.1 as "the certified version" of SoapUI, so trying a newer version is not a simple task for me. Can anyone confirm this, or explain to me what I'm doing wrong? :-)
Thanks in advance,
Stefan
i have a trouble, is there any games have no bugs?or no one found it 
