Forum Discussion
SmartBear_Suppo
Alumni
15 years agoHi,
this is probably related to how the browser component was used in 3.6.x, ie it would send a request of its own when showing the response. This has been fixed in the 4.0 release, so you should not see this behavior in that version, would it be possible for you to do a test-installation of 4.0 "on the side" just to confirm this?
To get around this in 3.6.1 you will have to disable the browser component - add -Dsoapui.jxbrowser.disable=true to the .vmoptions file (or soapui bat file if you are using that) in the soapUI bin folder.
Hope this helps,
regards,
/Ole
SmartBear Sweden
this is probably related to how the browser component was used in 3.6.x, ie it would send a request of its own when showing the response. This has been fixed in the 4.0 release, so you should not see this behavior in that version, would it be possible for you to do a test-installation of 4.0 "on the side" just to confirm this?
To get around this in 3.6.1 you will have to disable the browser component - add -Dsoapui.jxbrowser.disable=true to the .vmoptions file (or soapui bat file if you are using that) in the soapUI bin folder.
Hope this helps,
regards,
/Ole
SmartBear Sweden