possible to capture custom response header for http logs?

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:

Re: Tagging a 1.8 release?

On 20 October 2017 at 17:17, Willy Tarreau wrote: > I'd like to collect all the pending stuff by the end of next week and issue > a release candidate. Don't expect too much stability yet though, but your > tests and reports will obviously be welcome. Are you still finger-in-the-air

Re: [PATCH] MINOR: ssl: ocsp response with 'revoked' status is correct

Hi Willy, On 10/22/2017 10:02 AM, Willy Tarreau wrote: > Hi Manu, > > On Tue, Oct 10, 2017 at 03:44:07PM +0200, Emmanuel Hocdet wrote: >> Hi Emeric, >> >> >> ocsp_status can be 'good', 'revoked', or 'unknown'. 'revoked' status >> is a correct status and ocsp response should not be dropped. >> In

Re: Is there any best practice for setting tune.bufsize?

Hello, 2017-10-23 8:49 GMT+02:00 : > Hi, > > Is there any best practice for setting tune.bufsize? > > such as, leave it as is(16k), or never make it bigger than 1MB, something > like this? >From the documentation: > *It is strongly recommended not to change this from

Is there any best practice for setting tune.bufsize?

Hi, Is there any best practice for setting tune.bufsize? such as, leave it as is(16k), or never make it bigger than 1MB, something like this?

subscribe