httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Bloom <...@covalent.net>
Subject Re: Listen vs. Port
Date Fri, 10 Aug 2001 13:36:41 GMT
On Friday 10 August 2001 05:06, Bill Stoddard wrote:
> > On Thu, 9 Aug 2001, Cliff Woolley wrote:
> > > On Thu, 9 Aug 2001, Doug MacEachern wrote:
> > > > if Listen is used to set the server port, and Port is not configured,
> > > > ap_get_server_port returns the default port (80).  this breaks
> > > > mod_dir redirects if Listen is something other than 80.
> > >
> > > I thought that was the whole point of the Port directive in the first
> > > place.
> >
> > Sorry for stating the obvious, I missed the point of your message.  The
> > answer is still that this is the expected behaviour, though, at least
> > according to my reading of the docs for the Listen directive, which say:
> >
> > "Note that you may still require a Port directive so that URLs that
> > Apache generates that point to your server still work."
> >
> > <shrug>
>
> Bleh... We've had this discussion before and I think the conclusion was to
> get rid of the Port directive entirely.  The behaviour Doug reports is
> nonintuitive in the extreme and should be eliminated IHO.

You can not get rid of the Port directive.  It is an important directive that is there to
allow admins to configure their server to report a different port than it actually
uses.  This is the exact same as the ServerName directive, which is another
one that can't go away.

Ryan
_____________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
Covalent Technologies			rbb@covalent.net
-----------------------------------------------------------------------------

Mime
View raw message