Re: [PATCH 1/1] BUG/MAJOR: stick_table: Complete incomplete SEGV fix

On Wed, Jun 27, 2018 at 06:38:18AM +0200, Willy Tarreau wrote: > Tim, > > I've just added the following patch after finding another affected place > in smp_fetch_sc_trackers(). Fortunately this one couldn't happen, but the > checks on the code path definitely are wrong for the same reaons as in th

[ANNOUNCE] haproxy-1.8.12

Hi, HAProxy 1.8.12 was released on 2018/06/27. It added 2 new commits after version 1.8.11. Unfortunately the latest release didn't fix everything in the d7bd880 ("BUG/MEDIUM: stick-tables: Decrement ref_cnt in table_* converters"). There was still a segfault hidden in this fix. Users are encour

Re: [ANNOUNCE] haproxy-1.8.12

On 27/06/2018 16:33, William Lallemand wrote: Hi, HAProxy 1.8.12 was released on 2018/06/27. It added 2 new commits after version 1.8.11. Wow this was fast. Let's say it was agile ;-) Now the images are also ready. https://hub.docker.com/r/me2digital/haproxy18/ Regards Aleks Unfortunately

redirect vs. logging Location hdr

With a configuration having many 'redirect's (and wanting to know which 'Location' a given request was redirected to), I configured capture response header Location len 64 log-format %hs , but see no log entries for redirects I know haproxy is generating. With further testing, I know that Lo

Re: redirect vs. logging Location hdr

On Wed, Jun 27, 2018 at 04:08:27PM -0600, Jim Freeman wrote: > With a configuration having many 'redirect's (and wanting to know which > 'Location' a given request was redirected to), I configured > > capture response header Location len 64 > log-format %hs > > , but see no log entries for re

Re: redirect vs. logging Location hdr

Much thanks for the insights, clarifications, and solution possibilities. Will chew on this for a bit ... On Wed, Jun 27, 2018 at 10:40 PM, Willy Tarreau wrote: > On Wed, Jun 27, 2018 at 04:08:27PM -0600, Jim Freeman wrote: > > With a configuration having many 'redirect's (and wanting to know w