Good morning,
I am trying to load balance an WS connection through HAProxy to a Twisted /
Autobahn websocket server in the background.
On receiving the request the backend server complains that the Sec-WebSocket
-Key header key is too long and so drops the connection.
(bad Sec-WebSocket-Key (length must be 24 ASCII chars)
'53f6e3035a134a948fee7668f37129c73b7ce160'))
The key does indeed look too long. Is this something which HAProxy is
appending as a header at the time of moving between the original http
request on front end to the ws request on back end and if so is there some
way I can control it in order to ensure its the correct length?
Best regards,
Tom
I am trying to load balance an WS connection through HAProxy to a Twisted /
Autobahn websocket server in the background.
On receiving the request the backend server complains that the Sec-WebSocket
-Key header key is too long and so drops the connection.
(bad Sec-WebSocket-Key (length must be 24 ASCII chars)
'53f6e3035a134a948fee7668f37129c73b7ce160'))
The key does indeed look too long. Is this something which HAProxy is
appending as a header at the time of moving between the original http
request on front end to the ws request on back end and if so is there some
way I can control it in order to ensure its the correct length?
Best regards,
Tom