[PATCH] BUG/MINOR: cli: don't stop cli_gen_usage_msg() when kw->usage == NULL

In commit abbf607 ("MEDIUM: cli: Add payload support") some cli keywords without usage message have been added at the beginning of the keywords array. cli_gen_usage_usage_msg() use the kw->usage == NULL to stop generating the usage message for the current keywords array. With those keywords at the

Re: [PATCH] BUG/MINOR: cli: don't stop cli_gen_usage_msg() when kw->usage == NULL

On Tue, May 15, 2018 at 11:50:04AM +0200, William Lallemand wrote: > In commit abbf607 ("MEDIUM: cli: Add payload support") some cli keywords > without usage message have been added at the beginning of the keywords > array. (...) Applied, thank you William. Willy

RE: 502 Bad Gateway

Hi Alek/Haproxy Team, Any other way to effectively get the https proxy working ? Currently we are manually adding servers which is putting a limit to get the dynamic nature. Thanks, Praveen. -Original Message- From: Aleksandar Lazic [mailto:al-hapr...@none.at] Sent: Wednesday, May 09,

Re: 502 Bad Gateway

Hi Praveen. Am 15.05.2018 um 16:28 schrieb UPPALAPATI, PRAVEEN: > Hi Alek/Haproxy Team, > > Any other way to effectively get the https proxy working ? > > Currently we are manually adding servers which is putting a limit to get the > dynamic nature. Not with haproxy out of the box afaik, maybe

Re: Haproxy support for handling concurrent requests from different clients

Hi, On Fri, May 11, Mihir Shirali wrote: > I did look up some examples for setting 503 - but all of them (as you've > indicated) seem based on src ip or src header. I'm guessing this is more > suitable for a DOS/DDOS attack? In our deployment, the likelihood of > getting one request from multiple