Charles Sprickman wrote: > Hello all, > ~snip~ > > > So in short, this does work, until I get into the murky area of > keeping the URL consistent in the browser. For example, let's take > "www.foo.com". I always want visitors to see "www.foo.com" in the > browser URL field. If I set "UseCanonicalName On" in the virthosts, > the ServerName seems not to be enforced like it is with traditional IP > or name-based hosting. If I point "giantpornstash.blah.com" at the IP > that "www.foo.com" resolves to, the user will browse the site with > "giantpornstash.blah.com" in the browser address field. It is my > (limited) understanding that this should not happen with the > ServerName and UseCanonicalName settings properly configured, and > basically can't happen with Name-based virthosts (host header doesn't > match). > What am I missing? I suspect there's some issue here that is > DNS-related in that apache is unaware of the IP->port trickery the > firewall is using. Perhaps it sees that the IP each ServerName maps to > is not the IP it's listening on? I've been over the virthost and "dns > problems" sections of the docs, and what I'm doing is not clearly > addressed. > So I guess my questions are two: > > -Is port-based virtual hosting officially supported? yup > -How can I enforce setting the proper hostname in this scenario? > mod_rewrite to change the server name and remove the port from the url. far easier. Jaqui --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx