Le 10/18/22 à 18:24, William Dauchy a écrit :
On Tue, Oct 18, 2022 at 4:15 PM Christopher Faulet wrote:
On all HTX versions, K/A and close modes are handled in the H1 multiplexer.
Thus, on these versions, http_reply_and_close() is only closing the stream. The
multiplexer is responsible to
On Tue, Oct 18, 2022 at 4:15 PM Christopher Faulet wrote:
> On all HTX versions, K/A and close modes are handled in the H1 multiplexer.
> Thus, on these versions, http_reply_and_close() is only closing the stream.
> The
> multiplexer is responsible to close the client connection or not.
ok,
Hello,
hope this will help to catch some regression.
Ilya
From 90c8a08f627e62fb501ef214d4c1c6eccfef3c64 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Tue, 18 Oct 2022 19:13:45 +0500
Subject: [PATCH] CI: add monthly gcc cross compile jobs
Build only gcc cross compile jobs are added with
Le 10/18/22 à 13:01, William Dauchy a écrit :
Hi Christopher,
Thanks for your reply.
On Tue, Oct 18, 2022 at 10:22 AM Christopher Faulet wrote:
Since the 2.2, HAProxy responses don't close the client connections in K/A mode,
except for 400-Bad-Request and 408-Request-Time-out. It is the
There's an interesting case for OpenSSL-3.0, we do test it, but we run it
in "relaxed" mode, while
Ubuntu 22.04 and Fedora run it in SECLEVEL=2 mode.
that will definitely change when "ubuntu-latest" become 22.04, but we
should test it before
вт, 18 окт. 2022 г. в 18:28, Илья Шипицин :
>
>
> вт,
вт, 18 окт. 2022 г. в 17:40, William Lallemand :
> On Tue, Oct 18, 2022 at 03:10:07PM +0500, Илья Шипицин wrote:
> > > Sorry I didn't see the first commit that introduced this behavior. I'm
> > > not sure we would want to replace the version automatically in the CI
> > > for OpenSSL.
> > >
> >
>
On Tue, Oct 18, 2022 at 03:10:07PM +0500, Илья Шипицин wrote:
> > Sorry I didn't see the first commit that introduced this behavior. I'm
> > not sure we would want to replace the version automatically in the CI
> > for OpenSSL.
> >
>
> it was supposed behaviour for OPENSSL_VERSION=latest
>
Hi Christopher,
Thanks for your reply.
On Tue, Oct 18, 2022 at 10:22 AM Christopher Faulet wrote:
> Since the 2.2, HAProxy responses don't close the client connections in K/A
> mode,
> except for 400-Bad-Request and 408-Request-Time-out. It is the behavior with
> default error messages. Of
вт, 18 окт. 2022 г. в 14:46, William Lallemand :
> On Thu, Oct 13, 2022 at 08:54:38AM +0200, Willy Tarreau wrote:
> > Hi Ilya,
> >
> > On Tue, Oct 11, 2022 at 12:18:40PM +0500, ??? wrote:
> > > split patches attached.
> >
> > Sorry for the delay. Both applied now, thank you!
> > Willy
>
On Thu, Oct 13, 2022 at 08:54:38AM +0200, Willy Tarreau wrote:
> Hi Ilya,
>
> On Tue, Oct 11, 2022 at 12:18:40PM +0500, ??? wrote:
> > split patches attached.
>
> Sorry for the delay. Both applied now, thank you!
> Willy
>
Hello,
Sorry I didn't see the first commit that introduced
Hello,
While renewing a node.js servers and a galera cluster (mariadb) I'm
seeing an unexpected behaviour on TCP connections between node.js
application and mariadb.
There is a lot of connections resets during transfers on backend side.
My previous (working) setup was based on Debian 10,
Le 10/17/22 à 16:15, William Dauchy a écrit :
Hello,
I am trying to clarify in which case a tcp connection might be closed
following those rules:
- http-request return
- http-request deny
unless I missed something I have not been able to see the answer within the doc.
General context being, we
I really appreciate the response. This confirms, that "everything in
runtime mode" uses the same thread pool as HTTP workers. This also says
that the onlytime we can use "blocking IO" is in "initialization mode",
ie, at HAproxy startup/reloads.
Happy to help!
Considering what we've already
13 matches
Mail list logo
