Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-3276

Binary data does not decode correctly using the TJSONProtocol when the base64 encoded data is padded.

    XMLWordPrintableJSON

Details

    Description

      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 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.

      Attachments

        Issue Links

          Is contained by

          Bug - A problem which impairs or prevents the functions of the product. THRIFT-3359 Binary field incompatibilities

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. THRIFT-3359 Binary field incompatibilities

          • Major - Major loss of function.
          • Closed

          Activity

            People

              nsuke Nobuaki Sukegawa
              SteveNiemitz Steve Niemitz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: