tree 3f263c7ab37b96df159f9d026996b9eb82767baa
parent 5fb48ea7a43683df7a092f7215598324e548dee7
author Amaury Denoyelle <adenoyelle@haproxy.com> 1607705585 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1611848234 +0100

MEDIUM: h2: parse Extended CONNECT reponse to htx

Support for the rfc 8441 Bootstraping WebSockets with HTTP/2

Convert a 200 status reply from an Extended CONNECT request into a htx
representation. The htx message is set to 101 status code to be fully
compatible with the equivalent HTTP/1.1 Upgrade mechanism.

This conversion is only done if the stream flags H2_SF_EXT_CONNECT_SENT
has been set. This is true if an Extended CONNECT request has already
been seen on the stream.

Besides the 101 status, the additional headers Connection/Upgrade are
added to the htx message. The protocol is set from the value stored in
h2s. Typically it will be extracted from the client request. This is
only used if the client is using h1 as only the HTTP/1.1 101 Response
contains the Upgrade header.