Hi Tim, On Fri, Mar 11, 2022 at 07:24:42PM +0100, Tim Düsterhus wrote: > Willy, > > On 3/11/22 19:05, Willy Tarreau wrote: > > So unless anyone has extremely good insights about this or wants to > > share some return of experience from the field about similar issues, > > I'm going to work on this next week, trying to make this backportable > > to 2.5 at least. > > I don't have any insights to share, but as this touches an area that at > least is partly related to: > > https://github.com/haproxy/haproxy/issues/969
Ah indeed! > How is the current status of that one? I didn't even remember about it, there are far too many feature requests already :-( > I'm still interested in having that feature, Of course, I agree. > but it's likely out of reach for my current skill level within > HAProxy :-) I can easily understand. I don't know how to implement it either, it's complicated because streams are not supposed to act on the connection so there's no simple mechanism to do that (which is likely why it has been left that long with no progress). Something needs to be added to pass such a signal down the stack, in a way that remains compatible with the different versions. With HTTP/1 that's done by appending a "connection: close" header field, but I'm not much thrilled at the idea of making the H2 mux have a look at this one. I'll discuss this with Christopher who's still burried in all these intermediary layers, so that we can figure an elegant (hence durable) method to achieve this. Thanks for the reminder! Willy
