2016-05-28 12:25 GMT+02:00 Luca Toscano :
> Hi Yann,
>
> 2016-05-28 0:31 GMT+02:00 Yann Ylavic :
>
>> Hi Luca,
>>
>> On Mon, May 23, 2016 at 2:21 PM, Luca Toscano
>> wrote:
>> >
>> > I replied to the comment that you pointed
Hi Yann,
2016-05-28 0:31 GMT+02:00 Yann Ylavic :
> Hi Luca,
>
> On Mon, May 23, 2016 at 2:21 PM, Luca Toscano
> wrote:
> >
> > I replied to the comment that you pointed out with Jim's answer and I
> > updated the trunk documentation with a note
Hi Luca,
On Mon, May 23, 2016 at 2:21 PM, Luca Toscano wrote:
>
> 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
>
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:
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
> wrote:
>
> hi,
>
> in the comment section of
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?