SOAP Proxy problem

Skip to first unread message

Gunter Otté

Feb 5, 2021, 7:46:08 AM2/5/21
to membrane-monitor

I want to create a proxy for this target:

And my proxy seems to be ok, according the shown XML:

But, when I test with SOAP-UI, it is not working. Get NoHttpResponseException
This indicates that the server was not found, but when I copy/paste the link to my browser ( I get the expected response (XML).
I compared the returned endpoint XML of my proxy with the one of the target, and they look mostly the same. One thing I can see is that the returned XML of the proxy is starting with this:
<?xml version="1.0"?>
While the original target is starting with this:
<?xml version='1.0' encoding='UTF-8'?>
Could this be the issue?

Thanks for your help!


My router config in proxies.xml:
<keystore location="../../conf/rui.jks" password="" keyPassword="" />
<truststore location="../../conf/rui.jks" password="" />

This is the sample envelope:

This should return:
<soap:Envelope xmlns:soap="">
         <faultstring>Invalid username or password</faultstring>
            <ns2:AuthenticationFault xmlns:ns2="">Invalid username or password</ns2:AuthenticationFault>

Gunter Otté

Feb 5, 2021, 9:56:15 AM2/5/21
to membrane-monitor
I think the problem is here:

  <wsdl:service name="XTMWebService">
    <wsdl:port name="XTMProjectManagerMTOMWebServicePort" binding="tns:XTMWebServiceSoapBinding">

  <wsdl:service name="XTMWebService">
    <wsdl:port name="XTMProjectManagerMTOMWebServicePort" binding="tns:XTMWebServiceSoapBinding">

See the difference in soap:address.
Obviously, https is not the same as http:443.
Question is, how can I fix this?


Gunter Otté

Feb 5, 2021, 10:39:53 AM2/5/21
to membrane-monitor

Got a little bit further.
This is working:
<serviceProxy port="80">
<target host="" port="443">
<ssl />

This is not:

Is there something wrong with the wsdl processing? But when I run it through the validator ( it check out just fine.


Gunter Otté

Feb 11, 2021, 10:52:19 AM2/11/21
to membrane-monitor
I stopped trying with soapProxy, and concentrated myself on serviceProxy, which is able to do exactly what I want.
I'm not sure what I did wrong with soapProxy, or maybe it is getting depricated, no idea.


Reply all
Reply to author
0 new messages