On Tue, 15 May 2001, William A. Rowe, Jr. wrote:
> From: "Bill Stoddard" <[EMAIL PROTECTED]>
> Sent: Tuesday, May 15, 2001 11:08 AM
>
>
> > So you are saying this is a bug for sure? It is east to update
> > r->server->port with what is in the local_addr->sin_port field right before
> > calling new_connection(). There is code in http_main.c that does just that
> > for some platforms. Not sure what the implications are though...
>
> * general/3787: SERVER_PORT is always 80 if client comes to any port
> => needs review by the protocol guys, I think.
Suggestion: add a second, optional, argument to Listen which is the "real"
port this represents - I could have two (or more) "public" port numbers,
each with accelerators/load balancers/whatever proxying onto other port
numbers.
e.g. 80 -> 1080 (main WWW site)
8080 -> 1081 (some other application)
etc. The current Port/Listen split doesn't seem to allow this in an
obvious way?
James.
--
"Our attitude with TCP/IP is, `Hey, we'll do it, but don't make a big
system, because we can't fix it if it breaks -- nobody can.'"
"TCP/IP is OK if you've got a little informal club, and it doesn't make
any difference if it takes a while to fix it."
-- Ken Olson, in Digital News, 1988
