Open andyrichardson opened 3 years ago
API Gateway's current socket closing functionality doesn't support any kind of close code or close reason. Along with this, graphql-ws won't support error messages (which is understandable).
Feature request on AWS Discussion Forums
Because of this limitation, there is no clear way to communicate subprotocol errors to the client.
In the case of a subprotocol error the socket will be closed by the server (with no meaningful disconnect payload).
About
API Gateway's current socket closing functionality doesn't support any kind of close code or close reason. Along with this, graphql-ws won't support error messages (which is understandable).
Feature request on AWS Discussion Forums
Constraint
Because of this limitation, there is no clear way to communicate subprotocol errors to the client.
In the case of a subprotocol error the socket will be closed by the server (with no meaningful disconnect payload).