Request timed out when hitting parasoft.com:8080/examples/servlets/Echo
Hi,
I am trying to hit http://ws1.parasoft.com:8080/examples/servlets/Echo to echo my request (which has parameterized values ) and get a plain response. I am using the Mentioned end point from the past 3 months and now from last week I am getting a time out message on hitting the endpoint. Please help me with this issue.
Thanks,
Lakshmi.
Best Answer
-
Please use the echo.jsp provided with ParaBank. SOAtest includes a ParaBank example project which can be deployed locally. Alternatively, there is also the public deployment: http://parabank.parasoft.com/parabank/echo.jsp
The host ws1.parasoft.com is no longer publicly available. It has not been referenced in any documentation or tutorials since the SOAtest 9.8.0 release (Oct 24, 2014). The ParaBank demo application should be used instead.
5
Answers
-
Thank you for the info
0 -
Hi @benken_parasoft , is there a new host available to use the echo. i am getting 301 Moved permanently error on trying "http://parabank.parasoft.com/parabank/echo.jsp"
0 -
That link redirects to the HTTPS version - use this instead: https://parabank.parasoft.com/parabank/echo.jsp
0 -
The HTTP transport settings for Client tools has an option to "Follow HTTP redirects". This option is enabled by default for newly created tools. When enabled, the URI in the "Location" header of the 301 response is automatically requested.
0 -
@benken_parasoft i have the "Follow HTTP redirects" option selected but till getting the 301 response
0 -
i have the "Follow HTTP redirects" option selected but till getting the 301 response
Very odd. This doesn't happen for me.
when i use https i got "413 Request Entity Too Large" Response
You need to stand up your own version of ParaBank. It is included with SOAtest and is also available on github. The instance of ParaBank that is deployed at parabank.parasoft.com has extra security enabled that will block certain types of activity including sending of large message bodies.
0
