Forum Discussion
13 years ago
I ran into the same problem.
The issue seems to be in how SOAPUI handles a 302 redirect from the webserver.
In 3.6.1 and less, if you do a post and get a 302, SoapUI will do a Post to the next URL. In the versions greater than 3.6.1, after the 302 it will do a Get instead.
In my case, although the WSDL was from an HTTPS URL, the endpoint was set to HTTP. When SOAPUI did a POST using HTTP, it would get a 302 to redirect to HTTPS. As a workaround, I right clicked on my binding (interface) and chose "Show Interface Viewer". I then clicked on the Service Endpoints tab. I had one endpoint which I changed to https. I closed that window and went to my request and confirmed in the properties the endpoint was now https. When I ran the web service, it now works.
The issue seems to be in how SOAPUI handles a 302 redirect from the webserver.
In 3.6.1 and less, if you do a post and get a 302, SoapUI will do a Post to the next URL. In the versions greater than 3.6.1, after the 302 it will do a Get instead.
In my case, although the WSDL was from an HTTPS URL, the endpoint was set to HTTP. When SOAPUI did a POST using HTTP, it would get a 302 to redirect to HTTPS. As a workaround, I right clicked on my binding (interface) and chose "Show Interface Viewer". I then clicked on the Service Endpoints tab. I had one endpoint which I changed to https. I closed that window and went to my request and confirmed in the properties the endpoint was now https. When I ran the web service, it now works.