Forum Discussion

Frido's avatar
Frido
New Contributor
7 years ago

Version 5.4.0 handles "Follow Redirects" different from version 5.3.0 from SoapUI

When I run a specific test case, it succeeds with SoapUI 5.3.0 but fails with SoapUI 5.4.0. With the newer version, the Login POST request, receives an ERROR 500 from the server. The request must follow some redirects which is done well by version 5.3.0.

 

The POST request is a REST Test Step that implements a WADL method.

The SoapUI log displays another POST request after the response: HTTP/1.1 302 Moved Temporarily, but that POST should be a GET, which is done well by version 5.3.0.

 

Mon Mar 05 16:34:32 CET 2018:DEBUG:Stale connection check
Mon Mar 05 16:34:32 CET 2018:DEBUG:Attempt 1 to execute request
Mon Mar 05 16:34:32 CET 2018:DEBUG:Sending request: POST /IFM/j_spring_security_check HTTP/1.1
Mon Mar 05 16:34:32 CET 2018:DEBUG:Receiving response: HTTP/1.1 302 Moved Temporarily
Mon Mar 05 16:34:32 CET 2018:DEBUG:Connection can be kept alive indefinitely
Mon Mar 05 16:34:32 CET 2018:DEBUG:Stale connection check
Mon Mar 05 16:34:32 CET 2018:DEBUG:Attempt 1 to execute request
Mon Mar 05 16:34:32 CET 2018:DEBUG:Sending request: POST /IFM/engine/run.html?application=xml.r8-JJI_Portal&version=R5_0&channel=null&language=Nederlands&flow=startinteractief&style=IFM HTTP/1.1
Mon Mar 05 16:34:32 CET 2018:DEBUG:Receiving response: HTTP/1.1 500 Internal Server Error
Mon Mar 05 16:34:32 CET 2018:DEBUG:Connection can be kept alive indefinitely
Mon Mar 05 16:34:32 CET 2018:INFO:Got response for [http://t-ifm-app-01.org.jstd.local.j_spring_security_check:Login - POST Login] in 7ms (1208 bytes)
Mon Mar 05 16:34:32 CET 2018:DEBUG:Stale connection check

Regards,

Frido

No RepliesBe the first to reply