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
Network.WebSockets.Client doesn't appear able to connect to ports other than port 80 on Windows. I'm not sure what the behavior is on *nix, but servers that guard their websocket spec against the full combination of host:port/path would seem to reject the current behavior (servers that use guards against host/path would work successfully, as would host:80/path).
Network.WebSockets.Client
doesn't appear able to connect to ports other than port 80 on Windows. I'm not sure what the behavior is on *nix, but servers that guard their websocket spec against the full combination of host:port/path would seem to reject the current behavior (servers that use guards against host/path would work successfully, as would host:80/path).My reproduction case is:
main = withSocketsDo $ runClient2 "localhost" 80 "/Echo" app
runClientWith
function on line 66 to append the port to the host string when callingrunClientWithSocket
.runClientWith
should now look like this:runClientWithSocket sock (host ++ ":" ++ show port) path opts customHeaders app)
This seemed slightly related to issue #64, but with a different failure case. I'll submit a pull request with this change to
runClientWith
.The text was updated successfully, but these errors were encountered: