You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by yo...@apache.org on 2004/11/01 14:01:08 UTC

cvs commit: httpd-2.0/docs/manual/vhosts examples.xml

yoshiki     2004/11/01 05:01:08

  Modified:    docs/manual/vhosts examples.xml
  Log:
  Use <p></p> instead of <br> to mark paragraphs.
  
  Revision  Changes    Path
  1.12      +10 -6     httpd-2.0/docs/manual/vhosts/examples.xml
  
  Index: examples.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/vhosts/examples.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- examples.xml	19 Oct 2004 09:02:23 -0000	1.11
  +++ examples.xml	1 Nov 2004 13:01:08 -0000	1.12
  @@ -499,7 +499,9 @@
       href="#name">name-based</a> example, setup 2) should get its own IP
       address. To avoid problems with name servers or proxies who cached the
       old IP address for the name-based vhost we want to provide both
  -    variants during a migration phase.<br />
  +    variants during a migration phase.</p>
  +
  +    <p>
        The solution is easy, because we can simply add the new IP address
       (<code>172.20.30.50</code>) to the <code>VirtualHost</code>
       directive.</p>
  @@ -594,11 +596,13 @@
       <code>http://www.sub1.domain.tld/</code> is only
       served from the sub1-vhost if the client sent a correct
       <code>Host:</code> header. If no <code>Host:</code> header is sent the
  -    client gets the information page from the primary host.<br />
  -     Please note that there is one oddity: A request to
  +    client gets the information page from the primary host.</p>
  +
  +    <p>Please note that there is one oddity: A request to
       <code>http://www.sub2.domain.tld/sub1/</code> is also served from the
  -    sub1-vhost if the client sent no <code>Host:</code> header.<br />
  -     The <directive module="mod_rewrite">RewriteRule</directive> directives
  +    sub1-vhost if the client sent no <code>Host:</code> header.</p>
  +
  +    <p>The <directive module="mod_rewrite">RewriteRule</directive> directives
       are used to make sure that a client which sent a correct
       <code>Host:</code> header can use both URL variants, <em>i.e.</em>,
       with or without URL prefix.</p>