You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2016/06/22 10:43:34 UTC
svn commit: r1749650 -
/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml
Author: elukey
Date: Wed Jun 22 10:43:34 2016
New Revision: 1749650
URL: http://svn.apache.org/viewvc?rev=1749650&view=rev
Log:
Add mod-proxy DNS caching information to the documentation (follow up from users@)
Modified:
httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml
Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml?rev=1749650&r1=1749649&r2=1749650&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.xml Wed Jun 22 10:43:34 2016
@@ -303,6 +303,18 @@ ProxyPass "/examples" "http://backend.ex
Members are added to a balancer using
<directive module="mod_proxy">BalancerMember</directive>.</p>
+ <note><title>DNS resolution for origin domains</title>
+ <p>DNS resolution happens when the socket to
+ the origin domain is created for the first time.
+ When connection pooling is used, each backend domain is resolved
+ only once per child process, and reused for all further connections
+ until the child is recycled. This information should to be considered
+ while planning DNS maintenance tasks involving backend domains.
+ Please also check <directive module="mod_proxy">ProxyPass</directive>
+ parameters for more details about connection reuse.
+ </p>
+ </note>
+
</section> <!-- /workers -->
<section id="access"><title>Controlling Access to Your Proxy</title>