Dan Hammer wrote: > >In this case you'd still have to convince apache itself to service > >requests for www.host.com, which you could do by having 'order hosts, > >bind' in your /etc/host.conf, and then have a line mapping 192.168.x.x > >(whatever you picked for your server) to www.host.com. > > > >Note that you'll not be able to reach 207.168.x.x as www.host.com from > >that specific server. > > Ok... so it is more name dependent?
I should amend that... it can be. If you use NameVirtualHost (mapping multiple names on one IP) it is. If you have one IP per apache site the name doesn't matter beyond the fact that the visitors browser will use it for the initial resolve, and that midgard keys on whatever the browser sends in the host: header (which is the name the user types in the browser). > I was able to get the system > to prompt me for a password when attempting to access the admin page. > However once I entered the username and password the system tried > accessing the internal IP address instead of the real internet IP address. Hmmm... could be that the internal server keyed on it's IP address (depends on what you have set in the 'name' field in the host table) and it's sending a redirect. You will want to use the forced naming trick I suggested before, or one of the better alternatives others will inevitably suggest :) Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
