Rodent of Unusual Size wrote: > > When enabled, UseCanonicalName causes the server to > create any server-self-referential URLs using the name > by which it knows itself -- as opposed to what the client > may have called it. In many cases this is entirely > reasonable and good -- but it completely borks up the > ability to run on a non-default port.
Sorry, possibly a bit of missing info here: the canonicalisation currently forces the use of the server's own name for itself, and the *default* port for the scheme (e.g., 80 for http:, 443 for https:, ...). If the server is listening only on port 8080, the canonicalisation process will result in a useless and incorrect URL. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"
