[
https://issues.apache.org/jira/browse/MESOS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269584#comment-15269584
]
Alexander Rukletsov commented on MESOS-2013:
--------------------------------------------
Hey Whitney! I see that the problem can be annoying, but it does not seem it is
a critical production issue. As Ben pointed out above, we need to investigate
how to solve the issue in the context of JSON serialization in Mesos and not
just band-aid one particular aspect. We've already done several steps in this
directions, e.g., see MESOS-4235, but haven't finished yet, since we are
concentrating on different areas and tickets at the moment. Does it make sense?
> 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)
