Title: RE: Setting port for WS Client (No Firewall Proxy)

The issue is not the ports the server uses.  It will be expecting requests on ports 80 and 443.  The issue is that any HTTP client (browsers, Axis clients, etc.) opens a random port that is available, and not a well known port.  Yes, a proxy would probably remove the issue.  However, a proxy will not be available.  The client is being instantiated and called by another web server application.  The client makes a request on a remote web service outside of my control.

Is this a problem for any one who may be delegating work in a chain of services?

x -->X invokes y -->Y invokes z --> Z

Client x calls service X does some work and invokes client y to call service Y that invokes client z to call service Z.  The response returned to x is dependent on work done at X, Y & Z.   Where x is on server1, X and y are on server2, Y and z are on server3, and Z is on server4 AND all servers are in a unique domain with unique firewalls.

There has to be a better way than having proxies at each server/domain.

Regards,
Greg

Greg Bobak     
Cole National
http://www.thingsremembered.com

-----Original Message-----
From: Tom Oinn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 11, 2003 10:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Setting port for WS Client (No Firewall Proxy)

Surely if you want the client to use a particular port and you control
the server, don't you just set the server to run on that port? There is
no way the client can contact the server on any port other than the one
it's running on...

My advice would be to install a proper HTTP proxy server and configure
the client appropriately, you'll also need to tell it which machine the
proxy is running on and any hosts that the proxy should be bypassed for.
As a general rule just punching holes through your firewall leads to
some real security nightmares.

Tom

Bobak, Greg P. wrote:
> Using this:
>
> System.setProperty("http.proxyPort", proxy.port.here);
>
> Did not change the source port for the WS Client.
>
> Any suggestions are greatly appreciated.
>
>
> Greg Bobak    
http://www.thingsremembered.com
> -----Original Message-----
> From: Bobak, Greg P. [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 11, 2003 9:34 AM
> To: '[EMAIL PROTECTED]'
> Subject: Setting port for WS Client (No Firewall Proxy)
>
> Hi,
> I've searched the archive for this to no avail:
> I have an Axis client that will sit behind a tightly controlled
> firewall.  The service resides on an external IP -- I need to tell my
> network administrators which ports to open to that IP -- WE DO NOT HAVE
> A PROXY through the firewall.  Will this work to force the Axis client
> to use a select port:
>
> System.setProperty("http.proxyPort", proxy.port.here);
>
> If it does (I will check), are there any threading concerns (multiple
> clients running simultaneously hitting the same port)?
>
> Regards,
> Greg
> Greg Bobak    
> Cole National
> http://www.thingsremembered.com
>
>
> Privileged/Confidential Information may be contained in this message. If
> you are not the addressee indicated in this message (or responsible for
> delivery of the message to such person), you may not copy or deliver
> this message to anyone. In such case, you should destroy this message
> and kindly notify the sender by reply email. Please advise immediately
> if you or your employer do not consent to Internet email for messages of
> this kind. Opinions, conclusions and other information in this message
> that do not relate to the official business of my firm shall be
> understood as neither given nor endorsed by it.


Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.

Reply via email to