“ws” released 5.1.0 today (https://github.com/websockets/ws/releases) and I’m starting to see breakages in my functional tests after doing a complete reinstall via npm.
The error I’m getting from Autobahn is “Error: Unexpected server response: 400” which is coming from here (and it would be nice if the error was put into the “reason”):
https://github.com/crossbario/autobahn-js/blob/master/lib/transport/websocket.js#L144
Anyone else experiencing the same issue?
Regards,
Andrew Eddie
I can confirm rolling back to “ws” 5.0.0 fixes the problem.
Will this be an Autobahn problem or a WS problem?
Regards,
Andrew Eddie
Our test Crossbar is 17.5.1 btw.
Regards,
Andrew Eddie
Hi Eddie,
actually, this might be because of a bug introduced in ABJS with 18.3.1
and fixed with
https://github.com/crossbario/autobahn-js/pull/344
We've just pushed a hotfix release: AutobahnJS v18.3.2
Could you try that with your test set?
It works for me with ws 5.1
https://gist.github.com/oberstet/4efa5371ca5593796d46ad78df3ff768
Cheers,
/Tobias
Am 20.03.2018 um 02:17 schrieb Andrew Eddie:
"ws" released 5.1.0 today (https://github.com/websockets/ws/releases) and
I'm starting to see breakages in my functional tests after doing a complete
reinstall via npm.The error I'm getting from Autobahn is "Error: Unexpected server response:
400" which is coming from here (and it would be nice if the error was put
into the "reason"):
https://github.com/crossbario/autobahn-js/blob/master/lib/transport/websocket.js#L144Anyone else experiencing the same issue?
Regards,
Andrew Eddie