From: Luca Toscano <elukey@apache.org>
Date: Mon, 30 May 2016 06:47:40 +0000 (+0000)
Subject: Revert my previous doc commit about upstream DNS resolution caching in mod-proxy... 
X-Git-Tag: 2.4.21~111
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a3359aae812297531ddc9fb0366b3117c352a5aa;p=thirdparty%2Fapache%2Fhttpd.git

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
---

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 201eb706efd..e17cf7bdcf3 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -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>