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
The connection should be established with and without a trailing slash.
This works: WebSockex.start_link("ws://localhost", ...
This works: WebSockex.start_link("ws://localhost/not-root", ...
Remarks
Maybe this is an issue of my websocket server, rather than the WebSockex client?
However, the connection can be established by a different websocket client (Firefox weasel plugin).
Looking at the network trace of that plugin, it looks like it adds the trailing slash automatically in the HTTP request if it was not explicitly provided. Could that be a sensible approach for WebSockex as well?
The text was updated successfully, but these errors were encountered:
From a brief look at the weasel source I couldn't find any "add a trailing /" logic.
Probably the browser adds / as the default path.
ftes
changed the title
URL without trailing slash leads to %WebSockex.ConnError{original: :closed})
Root URL without trailing slash leads to %WebSockex.ConnError{original: :closed})
Nov 29, 2021
How to reproduce
WebSockex.start_link("ws://localhost", __MODULE__, nil)
Error:
reason: %WebSockex.ConnError{original: :closed}
Expected behaviour
The connection should be established with and without a trailing slash.
This works:
WebSockex.start_link("ws://localhost", ...
This works:
WebSockex.start_link("ws://localhost/not-root", ...
Remarks
Maybe this is an issue of my websocket server, rather than the
WebSockex
client?However, the connection can be established by a different websocket client (Firefox weasel plugin).
Looking at the network trace of that plugin, it looks like it adds the trailing slash automatically in the HTTP request if it was not explicitly provided. Could that be a sensible approach for
WebSockex
as well?The text was updated successfully, but these errors were encountered: