[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551592
]
Sangjin Lee commented on GERONIMO-3638:
---------------------------------------
Yes, I agree the default for URL encoding should be UTF-8. I also agree the
only case where anything other than UTF-8 could be used is to interact with a
server that may not be handling it properly and thus the client *has* to use a
different custom encoding.
I am changing the default URL encoding value to UTF-8, but proposing keeping an
option of setting the charset. I added an ample warning in the javadoc not to
... try this at home. :)
I'll upload a revised patch shortly...
> 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
> 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.
