bugfix/set character set on output stream writer to UTF 8 #15
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.
The existing HTTP client from cc.protea uses an
OutputStreamWriter
with the one-argument constructer, leading it to accept the system default character set.This presents issues as Hyperwallet accepts a certain character set, but does not know which characters the client's host OS supports by default.
The change sets the character set to UTF-8, which is in accordance with Hyperwallet specifications.
n.b. I highly recommend that Hyperwallet migrates away from using the
cc.protea
HTTP library. The library is useful in that it's syntactic sugar forHttpURLConnection
, but past that it's detrimental in terms of debuggability. I opened another pull request that also overrides a cc.protea class - and most of the functionality provided by thecc.protea
library would be replicated by allowing theHyperwalletApiClient
class to accept an HttpClient parameter.