You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2016/01/06 03:16:39 UTC
[jira] [Closed] (THRIFT-449) The wire format of the JSON Protocol
may not always be valid JSON if it contains non-UTF8 encoded strings
[ https://issues.apache.org/jira/browse/THRIFT-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Farrell closed THRIFT-449.
-------------------------------
Resolution: Won't Fix
Assignee: Jake Farrell
Fix Version/s: 0.9.4
closing as this has not had any traction since incubation, can reopen when more discussion and interest in this issue is warranted
> The wire format of the JSON Protocol may not always be valid JSON if it contains non-UTF8 encoded strings
> ---------------------------------------------------------------------------------------------------------
>
> Key: THRIFT-449
> URL: https://issues.apache.org/jira/browse/THRIFT-449
> Project: Thrift
> Issue Type: Bug
> Affects Versions: 0.1
> Reporter: Chad Walters
> Assignee: Jake Farrell
> Priority: Minor
> Fix For: 0.9.4
>
>
> Valid JSON is always Unicode. The JSONProtocol does not always have a wire format that conforms to this -- strings that are not UTF8 encoded can end up writing bytes into the transport that are not valid UTF8.
> I am trying to come up with a way to handle this that doesn't entail escaping every byte above 0x7F into a 6 byte escape sequence "\uXXXX". Suggestions welcomed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)