On Mon, 10 Mar 2003, Rich Bowen wrote: > > I was under the impression that Port was necessary in some situations, > > in just the same way as ServerName. For example, if you accept requests > > on many ports, but you always want to issue redirects to one particular > > port. > > This is not the case in practice. On my servers, I tend to run stuff on > several ports - for testing purposes or whatnot - and I never use Port > in my configurations, just Listen. However, I also always have > UseCanonicalName Off, so I may be just a little confused here too. I'll > experiment some more with this, and get back to you.
It's an issue when the server runs on a high port (say 127.0.0.1:8000), but users access it on port <routable ip>:80 (and then forwarded by the kernel or a front end proxy). Without the port statement, self referencing redirects (say from /dir to /dir/) will go out with port 8000 on them. - ask -- ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
