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,
Crossbar v18.11.1 is shiped with a config template using universal transport.
I mean when you do crossbar init , a folder is created with a basic config & the certificats.
When wampy client try to connect crossbar try to reconise a websocket client
in basis of the first byte => what he call "the magic Raw Socket byte"
2018-11-12T18:34:05+0100 [Router 21379 crossbar.router.unisocket.UniSocketServerProtocol] switching to HTTP on Request-URI //, mapping part
2018-11-12T18:34:05+0100 [Router 21379 crossbar.router.unisocket.UniSocketServerProtocol] no mapping found for request URI //, trying to map part
2018-11-12T18:34:05+0100 [Router 21379 crossbar.router.unisocket.UniSocketServerProtocol] client wants to talk HTTP/Web, but we have no factory configured for that
The text was updated successfully, but these errors were encountered:
to connect to an universal endpoint we need to append '/ws' at the end of the uri
ex : ws://127.0.0.1:8080/ws
using this url i am able to connect .
the issue can be close
hi,
Crossbar v18.11.1 is shiped with a config template using universal transport.
I mean when you do crossbar init , a folder is created with a basic config & the certificats.
When wampy client try to connect crossbar try to reconise a websocket client
in basis of the first byte => what he call "the magic Raw Socket byte"
see here => https://crossbar.io/docs/Transport-Endpoints/ (search on this page for Universal Listening Endpoints)
The text was updated successfully, but these errors were encountered: