Hi Christopher, On Fri, Feb 3, 2023 at 7:59 PM William Dauchy <wdau...@gmail.com> wrote: > On Tue, Oct 18, 2022 at 4:15 PM Christopher Faulet <cfau...@haproxy.com> > 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. > > > > On pre-HTX versions, when http_reply_and_close() is used, the client > > connection > > is also closed. It is a limitation of of HAProxy versions using the legacy > > HTTP. > > > > Note there is a case where the connection client may be closed. If the > > HAProxy > > response is returned before the end of the request, the client connection is > > closed. There is no (not yet) draining mode at the mux level. > > coming back on this very late: > > `http-request wait-for-body time` or a `http-request tarpit` mitigate > the draining issue? > I am trying to find a workaround on a setup where we are behind > another L7 LB where we unexpectedly close the connection.
saying another way, what is going the behaviour of `http-request return` if I have: http-request wait-for-body time 1s if CONDITION_A http-request deny if CONDITION_A Is it going to wait for the request, and so mitigate the mentioned drain limitation we currently have in the mux when `CONDITION_A` matches? -- William
