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
That means ws://localhost:1234 and ws://localhost:1234/?foo=bar do work fine but ws://localhost:1234?foo=bar doesn't work. I don't think URI's authority should have a trailing slash regardless of query string but am not quite sure in terms of specification. (However even Node.js's url module doesn't add a trailing slash to authority when formatting a url object.)
That means
ws://localhost:1234
andws://localhost:1234/?foo=bar
do work fine butws://localhost:1234?foo=bar
doesn't work. I don't think URI's authority should have a trailing slash regardless of query string but am not quite sure in terms of specification. (However even Node.js's url module doesn't add a trailing slash to authority when formatting a url object.)Anyway, ws 0.7.2 requires to do that and we need to work around it. The issue is reported to websockets/ws#258 and websockets/ws#386
The text was updated successfully, but these errors were encountered: