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/18 10:14:08 UTC
svn commit: r1748949 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
Author: elukey
Date: Sat Jun 18 10:14:08 2016
New Revision: 1748949
URL: http://svn.apache.org/viewvc?rev=1748949&view=rev
Log:
Documentation rebuild
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en?rev=1748949&r1=1748948&r2=1748949&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en Sat Jun 18 10:14:08 2016
@@ -342,13 +342,14 @@ ProxyPass "/examples" "http://backend.ex
<code class="directive"><a href="#balancermember">BalancerMember</a></code>.</p>
<div class="note"><h3>DNS resolution for origin domains</h3>
- <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 <code class="directive"><a href="#proxypass">ProxyPass</a></code>
- parameters).
- This means that httpd does not perform any DNS resolution caching.
+ <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 <code class="directive"><a href="#proxypass">ProxyPass</a></code>
+ parameters for more details about connection reuse.
</p>
</div>