You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 17, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -599,7 +599,6 @@ const instance = makeServer({
599
599
600
600
</details>
601
601
602
-
603
602
## Caveats
604
603
605
604
### Ping/Pong
@@ -609,3 +608,7 @@ For whatever reason, AWS API Gateway does not support WebSocket protocol level p
609
608
### Socket idleness
610
609
611
610
API Gateway considers an idle connection to be one where no messages have been sent on the socket for a fixed duration [(currently 10 minutes)](https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#apigateway-execution-service-websocket-limits-table). The WebSocket spec has support for detecting idle connections (ping/pong) but API Gateway doesn't use it. This means, in the case where both parties are connected, and no message is sent on the socket for the defined duration (direction agnostic), API Gateway will close the socket. A fix for this is to set up immediate reconnection on the client side.
611
+
612
+
### Socket Close Reasons
613
+
614
+
API Gateway doesn't support custom reasons or codes for WebSockets being closed. So the codes and reason strings wont match `graphql-ws`.
0 commit comments