]> granicus.if.org Git - apache/commitdiff
Adding a note to mod_proxy documentation to clarify DNS resolution with origin server...
authorLuca Toscano <elukey@apache.org>
Tue, 24 May 2016 11:41:57 +0000 (11:41 +0000)
committerLuca Toscano <elukey@apache.org>
Tue, 24 May 2016 11:41:57 +0000 (11:41 +0000)
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1745343 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/mod/mod_proxy.xml

index e17cf7bdcf331042d090ce4f2d6cf4961a9a4742..201eb706efd3b1b70c2a47812e1ae0a94b404324 100644 (file)
@@ -303,6 +303,17 @@ 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>