1 個回答
- 最新
- 最多得票
- 最多評論
0
When using WebSockets, the connection is established once using HTTP. From that point you send messages over the existing connections, not using HTTP protocol, so there are no HTTP headers and there are no request IDs.
There might be some ACK in the web sockets protocol itself, but if you want to be sure, you need to send an ACK from the backend.
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thanks, ok but i thought that AWS Apigateway had a way to override responseID in the socket messages itself. as it will already read the json in the sent message to get the route name, it could also read a requestID to use it instead of generating one.