-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with parsing WebSocket IPv6. #5326
Comments
|
Usually IPv6 address must be a string in square brackets, no? |
The bug is that eventually EDIT: this should be fixed in |
Ok. But what about problem with js-client? |
What about that? You mentioned Javascript in the headline but there is no description about that... |
@straight-shoota yes there is, at the bottom of the issue description. Regardless, seperate issues should be seperate github issues. Your second issue seems like something to investigate on gitter/irc/mailinglists though, instead of a concrete issue for the issue tracker. |
That last example is python...? |
Yes. After first problem look at line "Second error. (But i don't know where is the problem).". Create separate issue?
No answer in gitter. But ok, i will try again later. |
First problem. Crystal can't connect to IPv6 address. From client to server.
Server:
Client:
Error - https://gist.github.com/MrSorcus/d84c2a048aa629f251df08ad2662d7b9
Without URI.parse doesn't work too.
Second error. (But i don't know where is the problem). (resolved)Server:
Console.log show me ArrayBuffer(13) with byte length and without any payload.But! Python client (https://github.com/websocket-client/websocket-client) works fine.Binary receiving doesn't work in chromium & firefox.UPD: Problem with JS-client resolved. Look at here - https://stackoverflow.com/questions/47531467/why-js-client-doesnt-receive-binary-from-server/47532253#47532253
The text was updated successfully, but these errors were encountered: