-
Notifications
You must be signed in to change notification settings - Fork 586
UTF-8 decoding is wrong #74
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
Comments
My current workaround is to encode the message in JSON with ensure_ascii=True (I am using python for tests) |
I have gotten the decoding part to work by including functionality from: I introduced it in the compiled version of stomp.js, inside this.ws.onmessage. I don't have enough coffee-script skills to do an actual patch.
|
tobiassodergren
pushed a commit
to tobiassodergren/stomp-websocket
that referenced
this issue
Nov 21, 2014
tobiassodergren
pushed a commit
to tobiassodergren/stomp-websocket
that referenced
this issue
Nov 21, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When receiving an UTF-8 string with multi-byte characters like "é" "ю" etc. it is decoded byte by byte giving the result as:
é �
Sending doesn't work at all:
ùé
<<< PONG
The text was updated successfully, but these errors were encountered: