You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by dg...@hyperreal.org on 1997/11/12 22:12:00 UTC

cvs commit: apachen/htdocs/manual/vhosts ip-based.html name-based.html

dgaudet     97/11/12 13:11:59

  Modified:    htdocs/manual/vhosts ip-based.html name-based.html
  Log:
  Language tweaks.  Expand on the common reason why you would want to run
  multiple daemons.
  
  Revision  Changes    Path
  1.3       +19 -10    apachen/htdocs/manual/vhosts/ip-based.html
  
  Index: ip-based.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/vhosts/ip-based.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ip-based.html	1997/11/12 20:54:22	1.2
  +++ ip-based.html	1997/11/12 21:11:58	1.3
  @@ -36,13 +36,22 @@
   <p>
   Use multiple daemons when:
   <ul>
  -<li>The different virtual hosts need very different httpd configurations, such
  -   as different values for: <A HREF="../mod/core.html#servertype">ServerType</A>,
  -   <A HREF="../mod/core.html#user">User</A>,
  -   <A HREF="../mod/core.html#group">Group</A>,
  -   <A HREF="../mod/mod_mime.html#typesconfig">TypesConfig</A> or
  -   <A HREF="../mod/core.html#serverroot">ServerRoot</A>.
  -<li>The machine does not process a very high request rate.
  +<li>There are security partitioning issues, such as company1 does not want
  +    anyone at company2 to be able to read their data except via the web.
  +    In this case you would need two daemons, each running with different
  +    <A HREF="../mod/core.html#user">User</A>,
  +    <A HREF="../mod/core.html#group">Group</A>,
  +    <A HREF="../mod/core.html#listen">Listen</A>, and
  +    <A HREF="../mod/core.html#serverroot">ServerRoot</A> settings.
  +<li>You can afford the memory and
  +    <a href="../misc/descriptors.html">file descriptor requirements</a> of
  +    listening to every IP alias on the machine.  It's only possible to
  +    <A HREF="../mod/core.html#listen">Listen</A>
  +    to the "wildcard" address, or to specific addresses.  So if you have
  +    a need to listen to a specific address for whatever reason, then you
  +    will need to listen to all specific addresses.  (Although one httpd
  +    could listen to N-1 of the addresses, and another could listen to
  +    the remaining address.)
   </ul>
   Use a single daemon when:
   <ul>
  @@ -61,7 +70,7 @@
       Listen www.smallco.com:80
   </pre>
   It is recommended that you use an IP address instead of a hostname
  -(see <A HREF="../dns-caveats.html">DNS page</A>).
  +(see <A HREF="../dns-caveats.html">DNS caveats</A>).
   
   <h2>Setting up a single daemon with virtual hosts</h2>
   For this case, a single httpd will service requests for the main server
  @@ -95,7 +104,7 @@
   </pre>
   
   It is recommended that you use an IP address instead of a hostname
  -(see <A HREF="../dns-caveats.html">DNS page</A>).
  +(see <A HREF="../dns-caveats.html">DNS caveats</A>).
   
   <P>
   
  @@ -114,7 +123,7 @@
   <A HREF="../mod/core.html#namevirtualhost">NameVirtualHost</A>.
   <P>
   <A HREF="../mod/core.html#user">User</A> and
  -<A HREF="../mod/core.html#group">Group</A> maybe used inside a VirtualHost
  +<A HREF="../mod/core.html#group">Group</A> may be used inside a VirtualHost
   directive if the <A HREF="../suexec.html">suEXEC wrapper</A> is used.
   <P>
   
  
  
  
  1.2       +2 -2      apachen/htdocs/manual/vhosts/name-based.html
  
  Index: name-based.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/vhosts/name-based.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- name-based.html	1997/11/11 23:47:21	1.1
  +++ name-based.html	1997/11/12 21:11:59	1.2
  @@ -21,7 +21,7 @@
   
   <h2>Name-based vs. IP-based virtual hosts</h2>
   
  -<p>While the approach with IP-based virtual hosts works still very well,
  +<p>While the approach with IP-based virtual hosts works very well,
   it is not the most elegant solution, because a dedicated IP address
   is needed for every virtual host and it is hard to implement on some
   machines. The <code>HTTP/1.1</code> protocol contains a method for the
  @@ -55,7 +55,7 @@
   <p>The notable difference between IP-based and name-based virtual host
   configuration is the
   <A HREF="../mod/core.html#namevirtualhost"><code>NameVirtualHost</code></A>
  -directive which specifies any IP address that should be used as a target for
  +directive which specifies an IP address that should be used as a target for
   name-based virtual hosts.
   
   <p>Of course, any additional directives can (and should) be placed