On Tue, Oct 24, 2017 at 3:06 AM, Moemen MHEDHBI <[email protected]>
wrote:
> Hi David,
>
> Using "http-response set-header " and " capture response header" cannot
> grantee an execution order so that the header is captured at the right time.
>
> Can you try using this config in the following order:
>
> 1/ declare capture response len 12 id 0
> 2 http-response set-header X-R-ID %[res.hdr("X-Used-Params"),djb2(1),hex]
> 3/ http-response capture hdr(X-R-ID) id 0
>
> ++
>
>
that worked! thanks.
> On 24/10/2017 02:27, David Birdsong wrote:
>
> I'm using haproxy to create an identifier using an upstream response
> header like so:
>
> http-response set-header X-R-ID %[res.hdr("X-Used-Params"),djb2(1),hex]
>
> I'm having trouble getting haproxy to log this value with the additional
> capture header that should get routed to my custom http log:
>
> capture response header X-R-ID len 16
>
> Does http-response set-header run too late to be captured for logging?
>
>
> --
> Moemen MHEDHBI
>
>
