> For the Listen directive....
> The Apache online manual says:
> Note that you may still require a Port directive so that URLs that
> Apache generates that point to your server still work.
> but what does this mean .. i dont get it.
> why would the port directive be required to be mentioned, when the
> listen directive takes care of both the ip addr. and the port?
Sometimes Apache needs to generate an absolute URL refering to your
server. For example, if a client requests a directory without the
trailing slash, apache must send it a redirect that includes the
trailing slash. This redirect must include the absolute URL of the
server. To figure out what URL to use, apache looks at the ServerName
and Port directive (in 1.3; in 2.0 the ServerName directive covers
both functions). Normally you should just set Port to the
same port number that you used in Listen. The only exception
is people doing funny things with port-forwarding.
And the whole discussion is moot if you set "UseCanonicalName off", in
which case apache uses client-supplied values for the absolute URL.
--
Joshua Slive
Apache HTTP Server Users Mailing List: http://httpd.apache.org/userslist.html