[
https://issues.apache.org/jira/browse/THRIFT-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952116#comment-14952116
]
Hudson commented on THRIFT-3276:
--------------------------------
SUCCESS: Integrated in Thrift #1683 (See
[https://builds.apache.org/job/Thrift/1683/])
THRIFT-3276 Binary data does not decode correctly using the (roger: rev
a175437f66fa1a0b36233e7dd40b061d471276ff)
* lib/javame/src/org/apache/thrift/protocol/TJSONProtocol.java
* lib/cpp/src/thrift/protocol/TJSONProtocol.cpp
* test/known_failures_Linux.json
* lib/java/src/org/apache/thrift/protocol/TJSONProtocol.java
* lib/cpp/src/thrift/protocol/TJSONProtocol.h
* lib/csharp/src/Protocol/TJSONProtocol.cs
> 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: C++ - Library, Java - Library
> Affects Versions: 0.9.1
> Reporter: Steve Niemitz
> Assignee: Nobuaki Sukegawa
>
> 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)
