DrBacchus says Fix-a-docs-bug

PR 50396
Historical reasons for using IP-based virtualhosting no longer deserve
to be featured in our docs.

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

diff --git a/docs/manual/vhosts/name-based.xml b/docs/manual/vhosts/name-based.xml
index 964791d2bac6db59d517998f2d95eb88c18424f8..2c6fe4451f74388343cc007a50a43521c7b91fbc 100644 (file)
--- a/docs/manual/vhosts/name-based.xml
+++ b/docs/manual/vhosts/name-based.xml
@@ -48,25 +48,15 @@
     IP address and then configure the Apache HTTP Server to recognize
     the different hostnames. Name-based virtual hosting also eases
     the demand for scarce IP addresses. Therefore you should use
-    name-based virtual hosting unless there is a specific reason to
-    choose IP-based virtual hosting. Some reasons why you might consider
-    using IP-based virtual hosting:</p>
-
-    <ul>
-       <li>Name-based virtual hosting often <a href="../ssl/ssl_faq.html#vhosts">
-        cannot be used with SSL secure servers</a>
-        because of the nature of the SSL protocol.</li>
-
-        <li>Some operating systems and network equipment implement bandwidth
-        management techniques that cannot differentiate between hosts unless
-        they are on separate IP addresses.</li>
-    </ul>
+    name-based virtual hosting unless you are using equipment
+    that explicitly demands IP-based hosting.  Historical reasons for
+    IP-based virtual hosting based on client support are no longer
+    applicable to a general-purpose web server.</p>
 
     <p> Name-based virtual hosting builds off of the IP-based virtual host
     selection algorithm, meaning that searches for the proper server name
     occur only between virtual hosts that have the best IP-based address.</p>
 
-
 </section>
 
 <section id="alg"><title>How the server selects the proper name-based virtual host</title>