Skip to content
This repository was archived by the owner on Jul 10, 2024. It is now read-only.

I look that the Sec-WebSocket-Key inconsistent with the server response #126

Open
simonwanghub opened this issue Aug 6, 2020 · 0 comments

Comments

@simonwanghub
Copy link

--- request header ---
GET /api/v2/channels/samsung.remote.control HTTP/1.1
Upgrade: websocket
Host: 192.168.35.116:8001
Origin: http://192.168.35.116:8001
Sec-WebSocket-Key: Xhi+Wn7pn3FbOmssyQkG6Q==
Sec-WebSocket-Version: 13
Connection: upgrade


--- response header ---
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 3rADUUV+VGKaW0MqBwwSpMa4Mm0=

<websocket._app.WebSocketApp object at 0x102613ef0>
{"event":"ms.channel.timeOut"}
send: b'\x88\x82\x93S\x05\xe5\x90\xbb'
<websocket._app.WebSocketApp object at 0x102613ef0>

closed

How can i get Sec-WebSocket-Key and make sure the Settings are correct?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant