Commit 353618c2 authored by Luca Toscano's avatar Luca Toscano
Browse files

Revert my previous doc commit about upstream DNS resolution caching in... 

Revert my previous doc commit about upstream DNS resolution caching in mod-proxy, there is still confusion in the users@ mailing list about what is the real behavior.  



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1746084 13f79535-47bb-0310-9956-ffa450edef68
parent 20ebafba

docs/manual/mod/mod_proxy.xml

+0 −11
Original line number Diff line number Diff line
@@ -303,17 +303,6 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10 
      Members are added to a balancer using

      <directive module="mod_proxy">BalancerMember</directive>.</p>



      <note><title>DNS resolution for origin domains</title>

      <p>The DNS domain resolution happens when the socket to

        the origin server is created for the first time.

        When connection pooling is used, the DNS resolution is performed

        again only when the <code>ttl</code> of the connection expires

        (please check <directive module="mod_proxy">ProxyPass</directive>

        parameters).

        This means that httpd does not perform any DNS resolution caching.

        </p>

      </note>



    </section> <!-- /workers -->



    <section id="access"><title>Controlling Access to Your Proxy</title>