Re: unique-id-header set twice

2016-05-04 Thread Erwin Schliske
Hello, I described the case haproxy->application->haproxy. My preferred behavior would be that the header is set only if it is not present already. Our goal is tracing requests through our whole stack. This can be for example Haproxy --> Varnish --> Haproxy --> Application --> Backend We

Re: unique-id-header set twice

2016-04-30 Thread Willy Tarreau
On Sat, Apr 30, 2016 at 05:47:49PM +0100, Jonathan Matthews wrote: > On 29 Apr 2016 06:55, "Willy Tarreau" wrote: > > > > On Fri, Apr 22, 2016 at 04:37:04PM +0200, Erwin Schliske wrote: > > > Hello, > > > > > > for some of our services requests pass haproxy twice. As we have set the

Re: unique-id-header set twice

2016-04-30 Thread Jonathan Matthews
On 29 Apr 2016 06:55, "Willy Tarreau" wrote: > > On Fri, Apr 22, 2016 at 04:37:04PM +0200, Erwin Schliske wrote: > > Hello, > > > > for some of our services requests pass haproxy twice. As we have set the > > global option unique-id-header this header is added twice. [snip] > > I

Re: unique-id-header set twice

2016-04-28 Thread Willy Tarreau
On Fri, Apr 22, 2016 at 04:37:04PM +0200, Erwin Schliske wrote: > Hello, > > for some of our services requests pass haproxy twice. As we have set the > global option unique-id-header this header is added twice. > > Is there a way to avoid this? I could set the header with 'http-request >

unique-id-header set twice

2016-04-22 Thread Erwin Schliske
Hello, for some of our services requests pass haproxy twice. As we have set the global option unique-id-header this header is added twice. Is there a way to avoid this? I could set the header with 'http-request set-header', but ​ this cannot be configured globally. Thanks. Regards, Erwin​