dgaudet 97/04/28 13:11:26
Modified: htdocs/manual vhosts-in-depth.html
Log:
A grammar-o, a typo, and another What Works.
Revision Changes Path
1.5 +10 -5 apache/htdocs/manual/vhosts-in-depth.html
Index: vhosts-in-depth.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/vhosts-in-depth.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C3 -r1.4 -r1.5
*** vhosts-in-depth.html 1997/04/28 19:50:56 1.4
--- vhosts-in-depth.html 1997/04/28 20:11:25 1.5
***************
*** 179,185 ****
<h3>Vhost Matching</h3>
<p>
! The process by which vhost a request is for is as follows:
<p> <code>find_virtual_server</code>: When the connection is first made
by the client, the local IP address (the IP address to which the client
--- 179,185 ----
<h3>Vhost Matching</h3>
<p>
! The server determines which vhost to use for a request as follows:
<p> <code>find_virtual_server</code>: When the connection is first made
by the client, the local IP address (the IP address to which the client
***************
*** 278,284 ****
<p>Consider the config file above with three vhosts A, B, C. Suppose
that B is a named-based vhost, and A and C are IP-based vhosts. If
a request comes in on B or C's address containing a header
! "<SAMP>Host: A<SAMP>" then
it will be served from A's config. If a request comes in on A's
address then it will always be served from A's config regardless of
any Host: header.
--- 278,284 ----
<p>Consider the config file above with three vhosts A, B, C. Suppose
that B is a named-based vhost, and A and C are IP-based vhosts. If
a request comes in on B or C's address containing a header
! "<SAMP>Host: A</SAMP>" then
it will be served from A's config. If a request comes in on A's
address then it will always be served from A's config regardless of
any Host: header.
***************
*** 353,370 ****
<li>Place all main_server definitions before any VirtualHost definitions.
(This is to aid the readability of the configuration -- the post-config
merging process makes it non-obvious that definitions mixed in around
! virtualhosts might affect all virtualhosts.)
<li>Arrange your VirtualHosts such
that all name-based virtual hosts come first, followed by IP-based
! virtual hosts, followed by any <SAMP>_default_</SAMP> virtual host
<li>Avoid <code>ServerPaths</code> which are prefixes of other
<code>ServerPaths</code>. If you cannot avoid this then you have to
ensure that the longer (more specific) prefix vhost appears earlier in
the configuration file than the shorter (less specific) prefix
(<EM>i.e.</EM>, "ServerPath /abc" should appear after
! "ServerPath /abcdef").
</ul>
--- 353,375 ----
<li>Place all main_server definitions before any VirtualHost definitions.
(This is to aid the readability of the configuration -- the post-config
merging process makes it non-obvious that definitions mixed in around
! virtualhosts might affect all virtualhosts.)</p>
<li>Arrange your VirtualHosts such
that all name-based virtual hosts come first, followed by IP-based
! virtual hosts, followed by any <SAMP>_default_</SAMP> virtual host</p>
<li>Avoid <code>ServerPaths</code> which are prefixes of other
<code>ServerPaths</code>. If you cannot avoid this then you have to
ensure that the longer (more specific) prefix vhost appears earlier in
the configuration file than the shorter (less specific) prefix
(<EM>i.e.</EM>, "ServerPath /abc" should appear after
! "ServerPath /abcdef"). </p>
!
! <li>Do not use <i>port-based</i> vhosts in the same server as
! name-based vhosts. A loose definition for port-based is a vhost which
! is determined by the port on the server (<em>i.e.</em> one server with
! ports 8000, 8080, and 80 all of which have different configurations).</p>
</ul>
