[THRIFT-4446] JSONProtocol Base64 Encoding Trims Padding

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11.0
• Fix Version/s: 0.12.0
• Component/s: C# - Library, netcore - Library
• Patch Info: Patch Available
• Assignee: James E. King III
• Reporter: Allen
• Created: 09/Jan/18 17:44
• Updated: 02/Feb/19 13:47
• Resolved: 11/Jan/18 02:14

Description

In the C# and .NET Core libraries, the JSONProtocol's Binary Encoding to Base64 trims padding from the user provided byte arrays before encoding into Base64. This behavior is incorrect, as the user provided data should be encoded exactly as provided. Otherwise, data may be lost.

Fixed by no longer trimming padding on encode. Padding must still be trimmed on decode, in accordance with the Base64 specification.

For example:

• Before this patch, encoding the byte array [0x01, 0x3d, 0x3d] yields [0x01] upon decode. This is incorrect, as I should decode the exact data that I encoded.
• After this patch, it yields [0x01, 0x3d, 0x3d], as expected.

I have submitted a pull request here

Issue Links

• links to: GitHub Pull Request #1463