Closed christian-photo closed 2 years ago
Hello, @rennmaus-coder, thanks for using EmbedIO!
The presence of the Sec-WebSocket-Key
request header is mandated by RFC6455, that defines the WebSocket protocol. The value of this header is used by the server in the Sec-WebSocket-Accept
response header, so no, there is simply no way to establish a WebSocket connection without it.
If the client sending the request is a web browser, it is probably sending a normal GET request instead of a WebSocket request. There are different APIs involved on the Javascript side, i.e. you cannot establish a WebSocket request using XMLHttpRequest or fetch(): you have to use a WebSocket object instead. If you are using a client-side Javascript library, please check the library's documentation to see whether the classes / methods you use are expected to successfully establish a WebSocket connection; if so, you will probably have to file an issue with the library.
Describe the bug When I try to connect to my socket, I get a "500 - Internal Server Error"
The message says, that the header doesn't include a Sec-WebSocket-Key. My question is if I can "turn that off" by either configuring the websocket or disabling this Sec-WebSocket-Key check.
To Reproduce Not sure if it reproducable, but this is my WebServer:
this is my websocket:
Expected behavior I expect the browser to successfully connect to the socket and the socket to be sending messages
Desktop: