[ https://issues.apache.org/jira/browse/THRIFT-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646977#comment-14646977 ]
Steve Niemitz commented on THRIFT-3276: --------------------------------------- I haven't, but neither TBase64Utils.java nor TJSONProtocol.java have changed in any relevant way since 0.9.1. I suspect this was just never tested against a client that sends padded base64 strings. > Binary data does not decode correctly using the TJSONProtocol when the base64 > encoded data is padded. > ----------------------------------------------------------------------------------------------------- > > Key: THRIFT-3276 > URL: https://issues.apache.org/jira/browse/THRIFT-3276 > Project: Thrift > Issue Type: Bug > Components: Java - Library > Affects Versions: 0.9.1 > Reporter: Steve Niemitz > > If the base64 encoded JSON string has padding bytes at the end, the resulting > binary data returned in the thrift object ends up with extra padding bytes > (0xFF) at the end. > It seems like this is caused by the TJSONProtocol [using the padded > length|https://github.com/apache/thrift/blob/0.9.1/lib/java/src/org/apache/thrift/protocol/TJSONProtocol.java#L760] > when it tries to decode the last chunk, which results in the '=' being > converted into binary data. The DECODE_TABLE defaults to -1 (0xFF), which is > how it gets into the final output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)