GitHub user hirthwork opened a pull request:
https://github.com/apache/httpasyncclient/pull/2
Customizable CharsetDecoder in AsyncCharConsumer
Some servers doesn't specify Content-Type header, while sending response in
UTF-8. This change will allow to consume such servers responses properly.
Also, this will allow to specify content-type specific default charset. For
example, application/json rfc requires unicode representation, so for
json-responses UTF-8 can be used as the default charset.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hirthwork/httpasyncclient trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/httpasyncclient/pull/2.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2
----
commit 2dbcbbad103d478183fd2cd538bc06d93bb21c6b
Author: Dmitry Potapov <[email protected]>
Date: 2015-01-28T12:47:16Z
Customizable CharsetDecoder in AsyncCharConsumer
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
