[jira] [Commented] (MESOS-2013) Slave read endpoint doesn't encode non-ascii characters correctly

["Whitney Sorenson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269383#comment-15269383 ] 

Whitney Sorenson commented on MESOS-2013:
-----------------------------------------

Is there any chance of this being looked at or should we try to find a competent C++ developer to submit a patch?

> Slave read endpoint doesn't encode non-ascii characters correctly
> -----------------------------------------------------------------
>
>                 Key: MESOS-2013
>                 URL: https://issues.apache.org/jira/browse/MESOS-2013
>             Project: Mesos
>          Issue Type: Bug
>          Components: json api
>            Reporter: Whitney Sorenson
>
> Create a file in a sandbox with a non-ascii character, like this one: http://www.fileformat.info/info/unicode/char/2018/index.htm
> Hit the read endpoint for that file.
> The response will have something like: 
> data: "\u00E2\u0080\u0098"
> It should actually be:
> data: "\u2018"
> If you put either into JSON.parse() in the browser you will see the first does not render correctly but the second does.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)