W dniu 19.12.2025 o 13:32, Amaury Denoyelle pisze:
On Fri, Dec 19, 2025 at 01:10:16PM +0100, Hank Bowen wrote:
[...]
OK but the quoted fragment suggests that it is possible to have a single TCP
haproxy <-> server connection with streams (in case of HTTP/2 - HTTP/2
streams as I understand) of different sessions (although it would require at
least "aggressive" mode of http-reuse). But having considered that the
connection is recognized idle only after all requests have been sent and got
their entire responses, I cannot see any possibility for that.
Protocols such as HTTP/2 supports multiplexing, i.e. multiple
requests/responses can be exchanged in parallel. Thus, even if an HTTP/2
connection is not idle, it can be reused unless there is already too
many active streams on it. Such connections are labelled internally as
"available".
"Thus, even if an HTTP/2 connection is not idle, it can be reused" - OK,
everything is clear, that is the the crucial part, I assumed that each
haproxy <-> server TCP connection can only be reused by another session
if it is idle. Thank you both, Willy Tarreau and you for comprehensive
explanations!
BTW, this behavior is not identical for QUIC as the protocol does not
suffer from the same head-of-line blocking limitation, hence a
connection can be used in parallel by multiple sessions even in
http-reuse safe level.
