Commit 131763e5 authored by dgaudet's avatar dgaudet
Browse files

Language tweaks. Expand on the common reason why you would want to run 

multiple daemons.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@79587 13f79535-47bb-0310-9956-ffa450edef68
parent c3da628c

docs/manual/vhosts/ip-based.html

+16 −7
Changes for docs/manual/vhosts/ip-based.html: 16 added lines, 7 removed lines.
Original line number Diff line number Diff line
@@ -36,13 +36,22 @@ single daemon which supports all the virtual hosts. 
<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>,

<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/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.

    <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 @@ e.g. 
    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 @@ e.g. 
</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>

docs/manual/vhosts/name-based.html

+2 −2
Changes for docs/manual/vhosts/name-based.html: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -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 @@ code similar to the following:</p> 
<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

docs/manual/vhosts/name-based.html.en

+2 −2
Changes for docs/manual/vhosts/name-based.html.en: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -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 @@ code similar to the following:</p> 
<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