Update to Jackson 2.12 to resolve databind security issues #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: look into why Base64 encoding behavior has changed. Changed due to FasterXML/jackson-databind#2096.
Revert a change that switched to URL safe encoding. As byte[] and Blob per docs should never be used in query or path parameters (which are stuffed into the JSON body before parsing a request) rather ensure the existing behavior of Base64 encoding with padding being expected.