| commit | c193823343192014e7ebfe99a9bb1562c83ec81e | [log] [tgz] |
|---|---|---|
| author | Amaury Denoyelle <adenoyelle@haproxy.com> | Fri Dec 11 17:53:03 2020 +0100 |
| committer | Christopher Faulet <cfaulet@haproxy.com> | Thu Jan 28 16:37:14 2021 +0100 |
| tree | c73a6ffd3832292d90d24514b333df130082d837 | |
| parent | 18ee5c3eb0c8afc18627a0d9a096aabb4c61e34f [diff] |
MEDIUM: h1: generate WebSocket key on response if needed Add the Sec-Websocket-Accept header on a websocket handshake response. This header may be missing if a h2 server is used with a h1 client. The response key is calculated following the rfc6455. For this, the handshake request key must be stored in the h1 session, as a new field name ws_key. Note that this is only done if the message has been prealably identified as a Websocket handshake request.