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
Hi,
I'm interacting with Websocket server and the first step I have to implement is - authorize with sending websocket JSON packet. And I'm expecting answer contain Client ID some other connection related data
The problem I have experienced with - as all I send is combined into frames (?) the authorization request get sent only withing next iteraction backages and I got "not authorized" response.
It's been quite some time, however did you find a solution for this? I have a similar issue where I need to send an init message, get the ack and then send a subscribe, however I never catch the ack reply. the on('message') handler never gets called for some odd reason!?
Hi,
I'm interacting with Websocket server and the first step I have to implement is - authorize with sending websocket JSON packet. And I'm expecting answer contain Client ID some other connection related data
The problem I have experienced with - as all I send is combined into frames (?) the authorization request get sent only withing next iteraction backages and I got "not authorized" response.
The way I use Pawl (simplified)
is any way to enforce send ws request ?
The text was updated successfully, but these errors were encountered: