set JSON request body encoding to UTF-8 (it was ISO_8859_1 by default) #1
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.
per JSON specification JSON strings SHALL be encoded in UTF-8 (or other UTF encodings).
the constructor StringEntity(String) uses ISO_8859_1 encoding by default. This mistake leads to the error from szurubooru api: "Could not decode the request body. The JSON was incorrect or was not encoded as UTF-8" if json contains unusual symbols (like ×).
(the latest release does not implement any API that could be broken by this bug, I encountered it with my extended SzurubooruAPI that creates post with pre-defined tags and source:
So, if any tag or the source contains "×", the mentioned error will occur. This commit fixes that.