This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 340
INIT_FAIL message appears to not be properly formatted #88
Comments
@hmaurer ohhhh very good catch! Thank you for that! |
@Urigo The PR is quite instructive! Why was |
subscriptions-transport-ws/src/server.ts Lines 299 to 300 in fd0fcac
The INIT_FAIL just doesn't get to the client! |
baconz
pushed a commit
to PhiloInc/subscriptions-transport-ws
that referenced
this issue
Apr 24, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I am completely new to this project so this may just be the fruit of my incompetence, but it would appear that the
SubscriptionClient
expect anINIT_FAIL
message to contain apayload
field, c.f.subscriptions-transport-ws/src/client.ts
Line 287 in 7dba040
However, it seems that the server sets the
error
property directly on the message and not under apayload
field, c.f.subscriptions-transport-ws/src/server.ts
Line 161 in 7dba040
This lead to an error when I tried to use
connectionCallback
.Furthermore, upon rejection of the connection and if
connectionCallback
was not specified (to avoid the error), the client kept trying to reconnect without any backoff delay or limit on the number of reconnects.The text was updated successfully, but these errors were encountered: