Forum Discussion

guinitch's avatar
guinitch
14 years ago

Problem with 4.01, works in 3.6.1

I'm new to web services and working with a big company to connect to a web service of theirs. I downloaded SoapUI 4.0.1 and receive the message response below ("No content section present in the request"). I assumed it was an issue on their end, but after they suggested I try using 3.6.1 (which they are using), it worked. Again, the identical request sent through 4.0.1 failed and their experience is the same.

I can certainly test with 3.6.1, but this makes me wary that there may be something non-standard in their service that will cause me problems later. Any ideas? Thanks.


Message response:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>null</faultstring>
         <detail>
            <IBResponse type="error">
               <DefaultTitle>Integration Broker Response</DefaultTitle>
               <StatusCode>20</StatusCode>
               <MessageID>508</MessageID>
               <DefaultMessage>No content sections present in the request.</DefaultMessage>
               <MessageParameters/>
            </IBResponse>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

1 Reply

  • darryls99's avatar
    darryls99
    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.