[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-3638.
------------------------------------
Resolution: Fixed
Assignee: Rick McGuire
Committed revision 604018.
This last patch looks like it is the correct way to manage these encodings.
Thanks for sticking with this one.
> should allow URL encoding with custom encoding charset other than the default
> -----------------------------------------------------------------------------
>
> Key: GERONIMO-3638
> URL: https://issues.apache.org/jira/browse/GERONIMO-3638
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: AsyncHttpClient
> Affects Versions: 1.x
> Reporter: Sangjin Lee
> Assignee: Rick McGuire
> Attachments: 3638.patch
>
>
> Currently AsyncHttpClient uses Chartset.defaultCharset() when it encodes the
> query string. However, applications may want to use a different encoding
> than the machine default charset; e.g. UTF-8. It needs to provide a way to
> specify an encoding that AHC should use to encode the query string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
