Closed Zeroto closed 6 years ago
It seems that firefox includes keep-alive in the connection header causing Suave to send back a bad request during the websocket handshake
keep-alive
connection
Suave sends back a 400 bad request because it requires the connection header to be just Upgrade
Upgrade
Suave ignores the other values in the connection header and processes the connection upgrade
manually strip the other values from the connection header before sending the request to the handshake.
Hi @Zeroto I've pushed a new pre-release v2.5.0-beta2 with a fix. Please give it a try. Thanks.
Works ok now. Thanks 😄
Description
It seems that firefox includes
keep-alive
in theconnection
header causing Suave to send back a bad request during the websocket handshakeCurrent behaviour:
Suave sends back a 400 bad request because it requires the connection header to be just
Upgrade
Desired behaviour:
Suave ignores the other values in the
connection
header and processes the connection upgradeWorkaround
manually strip the other values from the connection header before sending the request to the handshake.