Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Tim Düsterhus
Thierry, Am 08.03.2018 um 21:15 schrieb Thierry Fournier: > Hey, the example of use of socket.http in attachment of your original > commit is great ! If you are curious what I built with that and in case you missed my list mail advertising the project:

Re: Need some help in HAPROXY setup.

2018-03-08 Thread Aleksandar Lazic
Hi Amit. Please keep the mailing list in loop, thanks. Am 08.03.2018 um 17:03 schrieb amit raj: > Hello Alex, > > Two things we have to achieve with the HAPROXY. > > 1.There should be no RSTs for closing the connection.(which is happening > when we are keeping option http-keep-alive in ur

Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Thierry Fournier
> On 8 Mar 2018, at 15:14, Tim Düsterhus wrote: > > Hi > > Am 08.03.2018 um 15:10 schrieb Thierry Fournier: >> Ok, Lua expect the number of elements ins the stack. The right way for >> returning 1 is: >> >> lua_pushinteger(L, 1); >>return 1; >> > > Okay, then my

Re: cppcheck finding

2018-03-08 Thread Olivier Houchard
Hi, On Thu, Mar 08, 2018 at 05:44:31PM +0100, Willy Tarreau wrote: > Hi, > > On Wed, Mar 07, 2018 at 03:26:25PM +0500, ??? wrote: > > Hello, > > > > [src/proto_uxst.c:160]: (warning) Redundant assignment of > > 'xfer_sock->next->prev' to itself. > > > > is it in purpose ? > > I

Re: Segmentation fault by ebtree.h

2018-03-08 Thread Willy Tarreau
On Thu, Mar 08, 2018 at 02:48:01PM +0800, aogooc xu wrote: > More debugging information ... > > (gdb) f 2 > #2 process_runnable_tasks () at src/task.c:229 > 229 rq_next = eb32_next(rq_next); > (gdb) print rq_next > $1 = (struct eb32_node *) 0x2a94840 > (gdb) print rq_next->node > $2 = {branches

Re: BUG/MINOR: limiting the value of "inter" parameter for Health check

2018-03-08 Thread Willy Tarreau
Hi Jonathan, On Wed, Mar 07, 2018 at 09:38:00PM +, Jonathan Matthews wrote: > On Wed, 7 Mar 2018 at 09:50, Nikhil Kapoor wrote > > > As currently, no parsing error is displayed when larger value is given to > > "inter" parameter in config file. > > > > After applying

Re: cppcheck finding

2018-03-08 Thread Willy Tarreau
Hi, On Wed, Mar 07, 2018 at 03:26:25PM +0500, ??? wrote: > Hello, > > [src/proto_uxst.c:160]: (warning) Redundant assignment of > 'xfer_sock->next->prev' to itself. > > is it in purpose ? I suspect it's a mistake and that it was meant to be xfer_sock->prev instead. CCing Olivier to

Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Tim Düsterhus
Hi Am 08.03.2018 um 15:10 schrieb Thierry Fournier: > Ok, Lua expect the number of elements ins the stack. The right way for > returning 1 is: > >lua_pushinteger(L, 1); > return 1; > Okay, then my patch probably worked, because of whatever value was left on the stack. I learned

Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Thierry Fournier
> On 8 Mar 2018, at 15:03, Tim Düsterhus wrote: > > Thierry, > > Am 08.03.2018 um 10:24 schrieb Thierry Fournier: >> I forgot 3 things while my first read: >> >> - The Lua error are not trigerred with a return 1 (the return 1 is a bug >> in the original function), but

Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Tim Düsterhus
Thierry, Am 08.03.2018 um 10:24 schrieb Thierry Fournier: > I forgot 3 things while my first read: > > - The Lua error are not trigerred with a return 1 (the return 1 is a bug >in the original function), but with something like that: > Your first patch will be regressing my commit

Re: lua socket api settimeout in seconds vs. milliseconds

2018-03-08 Thread Thierry Fournier
Hi Mark, Thanks, it seems perfect. But, I can’t apply on current master branch, the patch is rejected. I forgot 3 things while my first read: - The Lua error are not trigerred with a return 1 (the return 1 is a bug in the original function), but with something like that:

Re: Feature suggestion: Check for same binding on multiple frontends

2018-03-08 Thread Lukas Tribus
Hello, On 8 March 2018 at 06:36, Moomjian, Chad wrote: > Thanks for the information, Lukas. I'm confused why this is not a default > option though. Can you think of a time when you would ever want the exact > same binding in multiple places in the config? noreuseport