On Thu, 05 Sep 1996 12:54:14 -0700, Mike Berry-Porter
>Hi. Have a question regarding Apache/Httpd web page servers. I want to
>have a way of giving people different web pages who are part of
>different networks. ie. I want to give our local subnet (class c) users
>access to one such directory eg. "in-house web service" but anyone else
>(the rest of the Internet) will get a totally different webpage
>Can this be done?!
Quote:>Is it a feature of Apache/httpd, or is it something I need to look at
>from the network layer. (tcpwrap?) If so how? Or if none of these are
>possible, is it possible to "redirect" outside packets to another
>address, even though they were attempting to access the inside?
It is a feature of HTTP 1.1, supported by the latest release of Apache.
Look it up in the docs under "virtual host".
Quote:>I a little lost as to where I should head regarding this, so any help
>ata all would be greatly appreciated.
Basically, you can assign multiple host/domain names to a single IP
address, register them with your DNS, and have Apache display different
pages depending on which address is attempted. Same for multiple IP
addresses which point to a single physical host. The concept is a "virtual
host" or "virtual server". What you propose (ie, a different IP accessed
depending on whether one is accessing from the intranet or the internet) is
readily and quickly supported. You can also individually configure access
for each virtual server, to deny access from outside your intranet to the
internal site, and (if necessary) vice versa.
Multiple virtual hosts on a single IP requires HTTP 1.1 (latest Apache
(1.1?), and HTTP 1.1 compatible browsers (Netscape 1.1 is too early, 1.22
may be OK, 2.0+ is definitely OK).
Multiple virtual hosts on different IPs works with Apache 1.0+ and HTTP
1.0+ compatible browsers (basically everything).