[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546372
]
Jay D. McHugh commented on GERONIMO-3638:
-----------------------------------------
Content can be in any character set, but I am pretty sure that you are only
allowed to use a portion of the 8859 character set in URLs.
<snippet from RFC1738>
Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved
characters used for their reserved purposes may be used unencoded within a URL.
</snippet>
Since this is an HTTP client, shouldn't it be limited to the characters allowed
by the URL spec?
> 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: patch.zip
>
>
> 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.
