MartinE
16 years agoNew Contributor
[RESOLVED]SOAP Monitor and HTTP-Proxy
Hi all,
could need a helping hand with my proxy problem. I'm using lates SOUPUI 3.0.1 community on Windows XP.
I have the following sitiuation:
1) WebService consumer (client)
2) SOAP UI with SOAP Monitor configured as proxy on port 8081
3) local proxy (running on the computer where soap UI is running)
4) company proxy
5) webservice provider (server)
The webservice consumer is configured to use the soapui host as proxy, the service endpoint addresses are not changed, the webservice calls arrive there as i can see according messages in the log - so connection 1-2 is ok.
The "local proxy" is required as soapui does not play very well with our companies NTLM proxy for any reason (will be clarified with company IT). The global proxy configuration is ok - at least the WSDL query when creating a new soapUI project from "outside" works.
When calling the webservice from the client, i can see a timeout message in the command prompt of soapUI so the request gets stuck somewhere between 2 - 5. Could it be that soap monitor does not use the soapUI global proxy preferences?
Also tried to use tunneling without success :-(
Any hint would be greatly appreciated.
Regards,
Martin
could need a helping hand with my proxy problem. I'm using lates SOUPUI 3.0.1 community on Windows XP.
I have the following sitiuation:
1) WebService consumer (client)
2) SOAP UI with SOAP Monitor configured as proxy on port 8081
3) local proxy (running on the computer where soap UI is running)
4) company proxy
5) webservice provider (server)
The webservice consumer is configured to use the soapui host as proxy, the service endpoint addresses are not changed, the webservice calls arrive there as i can see according messages in the log - so connection 1-2 is ok.
The "local proxy" is required as soapui does not play very well with our companies NTLM proxy for any reason (will be clarified with company IT). The global proxy configuration is ok - at least the WSDL query when creating a new soapUI project from "outside" works.
When calling the webservice from the client, i can see a timeout message in the command prompt of soapUI so the request gets stuck somewhere between 2 - 5. Could it be that soap monitor does not use the soapUI global proxy preferences?
Also tried to use tunneling without success :-(
Any hint would be greatly appreciated.
Regards,
Martin