tree a80eaf9ace5f13e7a616d30509fe7fa0227b2bf4
parent 35d9053b6832c419f9a94ff331b5c495df1cde9d
author Amaury Denoyelle <adenoyelle@haproxy.com> 1674578541 +0100
committer Amaury Denoyelle <adenoyelle@haproxy.com> 1676888305 +0100

MEDIUM: h3: enforce GOAWAY by resetting higher unhandled stream

When a GOAWAY has been emitted, an ID is announced to represent handled
streams. H3 RFC suggests that higher streams should be resetted with the
error code H3_REQUEST_CANCELLED. This allows the peer to replay requests
on another connection.

For the moment, the impact of this change is limitted as GOAWAY is only
used on connection shutdown just before the MUX is freed. However, for
soft-stop support, a GOAWAY can be emitted in anticipation while keeping
the MUX to finish the active streams. In this case, new streams opened
by the client are resetted.

As a consequence of this change, app_ops.attach() operation has been
delayed at the very end of qcs_new(). This ensure that all qcs members
are initialized to support RESET_STREAM sending.

This should be backported up to 2.7.