tracker issue : CF-4199598

select a category, or use search below
(searches all categories and all time range)
Title:

WebSocket messages do not support non-ASCII characters in the case of websocket proxy

| View in Tracker

Status/Resolution/Reason: To Fix//BugVerified

Reporter/Name(from Bugbase): Mosh Teitelbaum / Mosh Teitelbaum ()

Created: 08/31/2017

Components: Web Socket

Versions: 2016,2018

Failure Type: Data Corruption

Found In Build/Fixed In Build: 2016,0,04,302561 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:
Sending a message that includes non-ASCII characters (unicode, emojis, etc.) results in the non-ASCII characters being replaced with multiple ASCII characters (ex., "?" was replaced with "Ω" ).  Similarly, when using the WebSocket proxy, the wsproxy.log file replaces these characters with question marks.


Steps to Reproduce:
Send a WS message with non-ASCII characters in it.


Actual Result:
Non-ASCII characters are replaced with multiple, ASCII characters.


Expected Result:
The message should be sent as expected.


Any Workarounds:
No

Attachments:

Comments: