Re: http-request do-resolve Woes

2019-10-30 Thread Baptiste
On Wed, Oct 30, 2019 at 4:48 PM David Birdsong wrote: > > On Wed, Oct 30, 2019 at 11:39 AM Baptiste wrote: > >> Thanks! >>> >>> It had that feel to it...seemed like a cache lock timeout and/or somehow >>> tied to the request interval. >>> >>> >> I think I know where to fix this behavior in the

Re: http-request do-resolve Woes

2019-10-30 Thread David Birdsong
On Wed, Oct 30, 2019 at 11:39 AM Baptiste wrote: > Thanks! >> >> It had that feel to it...seemed like a cache lock timeout and/or somehow >> tied to the request interval. >> >> > I think I know where to fix this behavior in the code. I will work on the > "how to fix it" later tonight. > In the

Re: http-request do-resolve Woes

2019-10-30 Thread Baptiste
> > Thanks! > > It had that feel to it...seemed like a cache lock timeout and/or somehow > tied to the request interval. > > I think I know where to fix this behavior in the code. I will work on the "how to fix it" later tonight. In the meantime, you can apply the workaround below. This is doable

Re: http-request do-resolve Woes

2019-10-30 Thread David Birdsong
On Wed, Oct 30, 2019, 9:58 AM Baptiste wrote: > > > On Tue, Oct 29, 2019 at 8:18 PM David Birdsong > wrote: > >> I should have put the haproxy version in the mail too: >> >> haproxy 2.0.8 >> >> On Tue, Oct 29, 2019 at 3:07 PM David Birdsong >> wrote: >> >>> I've narrowed down a behavior that I

Re: http-request do-resolve Woes

2019-10-30 Thread Baptiste
On Tue, Oct 29, 2019 at 8:18 PM David Birdsong wrote: > I should have put the haproxy version in the mail too: > > haproxy 2.0.8 > > On Tue, Oct 29, 2019 at 3:07 PM David Birdsong > wrote: > >> I've narrowed down a behavior that I think might be a bug, but is >> definitely not ideal. >> >> This

Re: http-request do-resolve Woes

2019-10-30 Thread Jarno Huuskonen
Hi, On Tue, Oct 29, David Birdsong wrote: > I've narrowed down a behavior that I think might be a bug, but is > definitely not ideal. > > This minimal configuration copies header: X-Host into Host and performs a > dynamic DNS query against that field name, stores the output in a txn var, > and

Re: http-request do-resolve Woes

2019-10-29 Thread David Birdsong
I should have put the haproxy version in the mail too: haproxy 2.0.8 On Tue, Oct 29, 2019 at 3:07 PM David Birdsong wrote: > I've narrowed down a behavior that I think might be a bug, but is > definitely not ideal. > > This minimal configuration copies header: X-Host into Host and performs a >

http-request do-resolve Woes

2019-10-29 Thread David Birdsong
I've narrowed down a behavior that I think might be a bug, but is definitely not ideal. This minimal configuration copies header: X-Host into Host and performs a dynamic DNS query against that field name, stores the output in a txn var, and then uses a backend whic sets the dest ip to that txn