httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: ServerPort directive
Date Mon, 14 Sep 1998 16:42:16 GMT
On Mon, 14 Sep 1998, Ben Laurie wrote:

> The ServerName directive is handy for a variety of reasons, but one in
> particular is for use where NAT or load-balancing stuff is between you
> and the 'net. However, we ran into a problem recently - where you map IP
> addresses on the outside to port numbers on the inside. This works fine
> until you hit an internally generated redirect - at which point the port
> number gets lost (ServerName preserves the external IP, but the internal
> port is used instead of the external one). To fix this problem we
> implemented a ServerPort directive, analogous to ServerName. I know I'm
> pushing my luck for 1.3.2, but, nevertheless, here it is.

Why exactly do you need a ServerPort directive?  Using the Port directive
with a Listen directive for that works for me.



Mime
View raw message