Hey Everyone,
I have a question about the *delay = yes* config flag and whether or not it caches the resolved IP after the initial connection? To give context, I want my load balancer (Haproxy) to forward requests to an app on Heroku, and I'm using stunnel on my LB box to proxy to Heroku via HTTPS. Since the IP for my app's endpoint could potentially change (60s DNS TTL), stunnel caching resolved IPs would be a problem.
Thanks,
John
On 2014-01-16 19:32, John Chow wrote:
I have a question about the /delay = yes/ config flag and whether or not it caches the resolved IP after the initial connection? To give context, I want my load balancer (Haproxy) to forward requests to an app on Heroku, and I'm using stunnel on my LB box to proxy to Heroku via HTTPS. Since the IP for my app's endpoint could potentially change (60s DNS TTL), stunnel caching resolved IPs would be a problem.
I specifically introduced the "delay" option to deal with dynamic IP addresses. Stunnel does not attempt to cache the IP addresses with "delay = yes". The local library may cache them, but it should honor the TTL.
Mike
-
John Chow -
Michal Trojnara