Contributions
ReadyAPI seems to be ignoring my Port on a POST request
I have a simple test login I am trying, my local server on my machine is using port 9443 (as shown in my endpoint), however when I press send, the login doesn't run and the raw shows the POST with the port removed. Two screen shots included: If I look at the logs I see the following: Tue Aug 09 16:20:35 EDT 2022: ERROR: org.apache.http.conn.HttpHostConnectException: Connect to elmwb.com:443 [elmwb.com/127.0.0.1] failed: Connection refused org.apache.http.conn.HttpHostConnectException: Connect to elmwb.com:443 [elmwb.com/127.0.0.1] failed: Connection refused at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:158) at com.eviware.soapui.impl.wsdl.support.http.SoapUiHttpClientConnectionOperator.connect(SoapUIMultiThreadedHttpConnectionManager.java:207) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpClient.doExecute(HttpClientSupport.java:272) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:617) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:591) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:337) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.followRedirects(HttpClientRequestTransport.java:388) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.followRedirects(HttpClientRequestTransport.java:395) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:261) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:130) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.Net.connect0(Native Method) at java.base/sun.nio.ch.Net.connect(Net.java:579) at java.base/sun.nio.ch.Net.connect(Net.java:568) at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) at java.base/java.net.Socket.connect(Socket.java:633) at com.eviware.soapui.impl.wsdl.support.http.SoapUISSLSocketFactory.connectSocket(SoapUISSLSocketFactory.java:234) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141) ... 23 more ===== Why is it not going to 9443?326Views0likes0CommentsRe: building test steps based on service discovery
Hey Rich, thanks for the quick response. Yes, they are fully defined endpoints, with potentially different hostnames. Based on your response it looks like I will need to look at Groovy, as I do need both URI and Parms to be dynamic. Thanks for the quick and detailed response.2 years agoPlace ReadyAPI QuestionsReadyAPI Questions601Views0likes0CommentsRe: building test steps based on service discovery
btw, In postman, I would parse the returned XML and pull out the additional service endpoints- place them into environment variables. I would then use those environment variables for the the endpoint in the next test step.2 years agoPlace ReadyAPI QuestionsReadyAPI Questions624Views0likes0Commentsbuilding test steps based on service discovery
This may be a very basic request, but I am trying to review ReadyAPI to see if I can use it to discover API Services, and then call those Services as part of my tests. Are there any examples of how to identify a URL from one API and use it as the API end point of the next step? My first API provides a catalog of the services available on the server in XML format.Solved639Views0likes3Comments