Hi Matthias, I replied to the comment that you pointed out with Jim's answer and I updated the trunk documentation with a note about DNS resolution:
http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#workers HTML diff only: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en?r1=1745170&r2=1745169&pathrev=1745170 Please let me know if the note is good enough, if so I'll update 2.4 documentation too. Jim: please let me know if the wording is correct, I used "when connection pooling is used" since earlier in the "Workers" section we have: "The two default workers have a fixed configuration and will be used if no other worker matches the request. They do not use HTTP Keep-Alive or connection pooling. The TCP connections to the origin server will instead be opened and closed for each request." Thanks! Luca 2016-05-22 15:48 GMT+02:00 Jim Jagielski <j...@jagunet.com>: > Since mod_proxy uses connection pooling, DNS is resolved when > the socket is 1st created and then when it is then re-created > as per the ttl of the connection pool itself. > > > On May 18, 2016, at 8:48 AM, Matthias Leopold <matth...@leopold.priv.at> > wrote: > > > > hi, > > > > in the comment section of > http://httpd.apache.org/docs/2.4/mod/mod_proxy.html someone asks: > > > > It is unclear from this documentation, when does Apache do DNS resolving > of the origin server hostname? At each request? Does Apache do DNS caching? > If yes, for how long? Does it honour TTL? > > > > unfortunately there was no answer, i'd like to know the same thing > > > > thx > > matthias > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
