httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/misc FAQ-E.html
Date Thu, 08 Nov 2001 15:58:32 GMT
slive       01/11/08 07:58:32

  Modified:    htdocs/manual/misc FAQ-E.html
  Log:
  Make this a little closer to valid xhtml.
  
  Revision  Changes    Path
  1.13      +25 -26    httpd-docs-1.3/htdocs/manual/misc/FAQ-E.html
  
  Index: FAQ-E.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/FAQ-E.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -d -b -u -r1.12 -r1.13
  --- FAQ-E.html	2001/11/08 15:53:11	1.12
  +++ FAQ-E.html	2001/11/08 15:58:31	1.13
  @@ -33,7 +33,7 @@
       <h1 align="CENTER">Apache Server Frequently Asked
       Questions</h1>
   
  -    <p>$Revision: 1.12 $ ($Date: 2001/11/08 15:53:11 $)</p>
  +    <p>$Revision: 1.13 $ ($Date: 2001/11/08 15:58:31 $)</p>
   
       <p>The latest version of this FAQ is always available from the
       main Apache web site, at &lt;<a
  @@ -659,15 +659,14 @@
           so that they see only a single name?</strong></a></li>
   
           <p>Many sites map a variety of hostnames to the same content.
  -	(This differs from <a href="../vhosts/">virtual hosting</a> where
  -	different hostnames map to different content.)  For example,
  -        <code>www.example.com</code>, <code>example.com</code>
and
  -        <code>www.example.net</code> may all refer to the same site.
  -	It is best to make sure that, regardless of the name clients
  -	use to access the site, they will be redirected to a single,
  -	canonical hostname.  This makes the site easier to maintain
  -	and assures that there will be only one version of the site
  -	in proxy caches and search engines.</p>
  +        For example, <code>www.example.com</code>,
  +        <code>example.com</code> and <code>www.example.net</code>
may
  +        all refer to the same site.  It is best to make sure that,
  +        regardless of the name clients use to access the site, they
  +        will be redirected to a single, canonical hostname.  This
  +        makes the site easier to maintain and assures that there will
  +        be only one version of the site in proxy caches and search
  +        engines.</p>
   
           <p>There are two techniques to implement canonical hostnames:</p>
   
  @@ -680,20 +679,20 @@
   	  virtual hosting</a>:
   
   <blockquote><code>
  -NameVirtualHost *<br>
  -<br>
  -&lt;VirtualHost *&gt;<br>
  -&nbsp;&nbsp;ServerName www.example.net<br>
  -&nbsp;&nbsp;ServerAlias example.com<br>
  -&nbsp;&nbsp;Redirect permanent / http://www.example.com/<br>
  -&lt;/VirtualHost&gt;<br>
  -<br>
  -&lt;VirtualHost *&gt;<br>
  -&nbsp;&nbsp;ServerName www.example.com<br>
  -&nbsp;&nbsp;DocumentRoot /usr/local/apache/htdocs<br>
  +NameVirtualHost *<br />
  +<br />
  +&lt;VirtualHost *&gt;<br />
  +&nbsp;&nbsp;ServerName www.example.net<br />
  +&nbsp;&nbsp;ServerAlias example.com<br />
  +&nbsp;&nbsp;Redirect permanent / http://www.example.com/<br />
  +&lt;/VirtualHost&gt;<br />
  +<br />
  +&lt;VirtualHost *&gt;<br />
  +&nbsp;&nbsp;ServerName www.example.com<br />
  +&nbsp;&nbsp;DocumentRoot /usr/local/apache/htdocs<br />
   &lt;/VirtualHost&gt;
   </code></blockquote>
  -       </ol>
  +          </li></ol>
           <hr /></li>
       </ol>
       <!--#endif -->
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message