On Fri, 7 Sep 2001, Joe Pearse wrote:
> Date: Fri, 07 Sep 2001 16:49:09 -0700
> From: Joe Pearse <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Specify outbound port on tomcat
>
> The application itself is generating the message being sent out. In the
> basic sense, a browser is not involved. For example, information is
> received on port 443, and processed by the application. From that, a
> java.net.URL object is created, and the message is fired off to the
> specified client URL. When firing off the message, the outbound port
> (1024-5000) is chosen, and I'm not sure what chooses the port, and if I can
> restrict it.
OK, to make an outbound connection, you definitely need a port on the
local server. But what matters to a firewall is the port on the
*destination* of that connection, not the *origin*. What port number on
the client are you sending to? In order for things to work, *this* is the
port number your firewall has to allow through (assuming that the client
is on the other side of it, of course).
Which, of course, raises the question of why do this anyway, when you can
simply return data in the HTTP response to the request you are processing,
but that's a different question.
Craig
