You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This affects at least 2.6.4 to current versions. In TreeTraversingParser#getBinaryValue, a Base64Variant is accepted but ignored. The call to n.binaryValue(), when n is a TextNode, then uses the default Base64 variant instead of what's specified. It seems the correct behavior would be to call TextNode#getBinaryValue instead.
The text was updated successfully, but these errors were encountered:
byte[] data = n.isTextual()
? ((TextNode) n).getBinaryValue(b64variant)
: n.binaryValue();
That seems sufficient, though I am operating on 2.6 and it looks like ObjectMapper has undergone a lot of refactoring since then. Presumably it would propagate the variant down correctly to the method.
cowtowncoder
changed the title
TreeTraversingParser does not take base64 variant into accountTreeTraversingParser does not take base64 variant into account
Aug 15, 2018
This affects at least 2.6.4 to current versions. In TreeTraversingParser#getBinaryValue, a
Base64Variant
is accepted but ignored. The call ton.binaryValue()
, whenn
is aTextNode
, then uses the default Base64 variant instead of what's specified. It seems the correct behavior would be to callTextNode#getBinaryValue
instead.The text was updated successfully, but these errors were encountered: