That worked. I edited the /etc/host file on the linux client with a public IP, and I can get access to the 3rd vhost. Finally, get back to the original issue which started all this.
I need to be able expose the site to certain decision makers while its under development. Hence why I tried Order, Deny, Allow directives for a public IP. I can't edit their individual /etc/hosts files. Any other way to help Apache route to the 3rd vhost until I can get a FQDN? On Tue, Jun 25, 2013 at 11:22 AM, Eric Covener <cove...@gmail.com> wrote: > On Tue, Jun 25, 2013 at 11:12 AM, Kirk Woellert <kdwo...@gmail.com> wrote: > > Ok, there are two clients in this thread, 1 is the client on the server > > console and is my personal linux system which is on the Internet. The > > /etc/hosts file on the server has an entry so that the alias in the vhost > > block resolves when testing on the server. Are you saying I need to edit > the > > /etc/hosts file on my linux pc? > > Yes. If you want to use a hostname to discriminate between virtual > hosts, your client has to use that hostname. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
