tree 256a4fd65e1a5b25b1b04e55abb1e7f910ddfe73
parent 5b82cc5b5c350c7cfa194cc6bc16ad9308784541
author Amaury Denoyelle <adenoyelle@haproxy.com> 1607705582 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1611848234 +0100

MINOR: h1: reject websocket handshake if missing key

If a request is identified as a WebSocket handshake, it must contains a
websocket key header or else it can be reject, following the rfc6455.

A new flag H1_MF_UPG_WEBSOCKET is set on such messages.  For the request
te be identified as a WebSocket handshake, it must contains the headers:
  Connection: upgrade
  Upgrade: websocket

This commit is a compagnon of
"MEDIUM: h1: generate WebSocket key on response if needed" and
"MEDIUM: h1: add a WebSocket key on handshake if needed".

Indeed, it ensures that a WebSocket key is added only from a http/2 side
and not for a http/1 bogus peer.