Commit 3812346f authored by Nick Kew's avatar Nick Kew
Browse files

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/branches/2.2.x@1066435 13f79535-47bb-0310-9956-ffa450edef68
parent e9131820

docs/manual/vhosts/name-based.xml

+6 −20
Changes for docs/manual/vhosts/name-based.xml: 6 added lines, 20 removed lines.
Original line number Diff line number Diff line
@@ -48,26 +48,12 @@ 
    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>Some ancient clients are not compatible with name-based virtual

        hosting.  For name-based virtual hosting to work, the client must send

        the HTTP Host header.  This is required by HTTP/1.1, and is

        implemented by all modern HTTP/1.0 browsers as an extension.  If you

        need to support obsolete clients and still use name-based virtual

        hosting, a possible technique is discussed at the end of this

        document.</li>



        <li>Name-based virtual hosting cannot be used with SSL secure servers

        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, unless you are

    using a <module>mod_ssl</module> version without SNI support

    (standard in Apache releases since 2.2.12).</p>



</section>