tree a3c31a6d96cdde32cb107ab412cbd70c972eca5e
parent b6af6b3650a6a1209ba503b6937afef2c08402e8
author Baptiste Assmann <bedis9@gmail.com> 1572448013 +0100
committer Willy Tarreau <w@1wt.eu> 1573148894 +0100
encoding latin1

BUG/MINOR: action: do-resolve now use cached response

As reported by David Birdsong on the ML, the HTTP action do-resolve does
not use the DNS cache.
Actually, the action is "registred" to the resolution for said name to
be resolved and wait until an other requester triggers the it. Once the
resolution is finished, then the action is updated with the result.
To trigger this, you must have a server with runtime DNS resolution
enabled and run a do-resolve action with the same fqdn AND they use the
same resolvers section.

This patch fixes this behavior by ensuring the resolution associated to
the action has a valid answer which is not considered as expired. If
those conditions are valid, then we can use it (it's the "cache").

Backport status: 2.0

(cherry picked from commit 7264dfe9495a7bfd784b8964508e4204b7e077af)
Signed-off-by: Willy Tarreau <w@1wt.eu>