You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Eric Carlson <st...@blueyonder.co.uk> on 2002/09/06 01:45:09 UTC
Can only access soap service locally
Hi,
I have a simple soap service running on W2k under resin on port 8080.
The machine is also running apache on port 80. I have a client on a
separate pc (but still on the lan) which constructs the soap call with
a url of "http://reggae:8080/soapserver/servlet/rpcrouter" - this
works. The server is an internet facing machine, reggae is its local
name. On my client when I replace the word "reggae" with the real url
and activate setProxyHost("reggae"), setProxyPort(8088) (the correct
values to proxy out from the client to the net) I get back a whole
load of regular html telling me "object not found". The message
actually comes from apache running on port 80! I know this because
when I stop it the error changes to "no route to host". To test
further I ran the client on the server without the proxy and got
exactly the same message. What gives here please - anyone seen a
similar pattern?
One nagging suspicion - this is a cable modem server at home. Could my
ISP be somehow blocking soap calls?
Thanks!
<*> Windows XP: How many total strangers do you want poking around in your PC today? <*>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>