Open anotheri opened 3 years ago
Hi @anotheri, I haven't verified but I believe you that this is not working. I currently don't have time to work on this. I'd be happy to receive a PR though.
Just a note: this might be a bug in the wss
package.
this might be a bug in the
wss
package.
Well, it's possible but I doubt it, b/c I have another wss defined with path: '/ws'
, which works as expected. But I define path
on the client-side as well.
So to me, it looks like the only difference between these ones that the client for y-websocket
created w/o path
property.
Also have no time right now to verify this further and prepare PR. :/
But I'll try to prepare PR as soon as I have a chance.
Cool, thanks :+1:
Describe the bug I can't see the way to define the
path
property for the WebSocket client. When I use URL or room to emulate thepath
value to match URL, requests go to the server, but the connection never setup as expected. It never passes thehandleUpgrade
method.To Reproduce Server:
and on the client (I tried different combinations but the connection is dropping anyway)
Expected behavior I expect to have a way to define the same
path
I use on the WS server and that would establish the connection as expectedEnvironment Information
Huly®: YJS-513