Re: Generic backend in HAProxy config with server options as placeholders

On Thu, Nov 15, 2018 at 4:07 AM Igor Cicimov wrote: > > > On Thu, Nov 15, 2018 at 1:36 AM Aleksandar Lazic > wrote: > >> Hi Vijay. >> >> Am 14.11.2018 um 10:14 schrieb Vijay Bais: >> > Hello Aleksandar, >> > >> > We already considered using haproxy maps but we still have to define N >> backends

Re: Generic backend in HAProxy config with server options as placeholders

On Thu, Nov 15, 2018 at 1:36 AM Aleksandar Lazic wrote: > Hi Vijay. > > Am 14.11.2018 um 10:14 schrieb Vijay Bais: > > Hello Aleksandar, > > > > We already considered using haproxy maps but we still have to define N > backends > > for corresponding N keys in the map file. > > I'm looking more at

[PATCH] BUG/CRITICAL: SIGBUS crash on aarch64

Atomic operations on aarch64 (arm64) have to be aligned to 8 byte boundaries (same size as a pointer type), otherwise a SIGBUS is raised. Because the variable ts here isn't guaranteed to be aligned due to the various data_size adjustments, make sure that data_size is always incremented by a

haproxy segfaults when clearing the input buffer via LUA

Hi, I was playing with LUA, to configure a traffic mirroring behavior. Basically I wanted HAProxy to send the http response of a request to a 3rd party before sending the response to the client. So this is the stripped down version of the script to reproduce the segfault with haproxy from the

Re: Generic backend in HAProxy config with server options as placeholders

Hi Vijay. Am 14.11.2018 um 10:14 schrieb Vijay Bais: > Hello Aleksandar, > > We already considered using haproxy maps but we still have to define N > backends > for corresponding N keys in the map file. > I'm looking more at an implementation with single backend definition with the > server

Re: Generic backend in HAProxy config with server options as placeholders

Hello Aleksandar, We already considered using haproxy maps but we still have to define N backends for corresponding N keys in the map file. I'm looking more at an implementation with single backend definition with the server options as placeholders. Ex. Using maps would look something like this

Re: Generic backend in HAProxy config with server options as placeholders

Hi. Am 14.11.2018 um 08:46 schrieb Vijay Bais: > Hello, > > We have a requirement wherein a single generic backend with server options > configured as placeholders, which will resolve on the fly or at runtime. > > Currently, we have to define multiple backends (has to be hardcoded) and >