geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay D. McHugh (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3638) should allow URL encoding with custom encoding charset other than the default
Date Wed, 28 Nov 2007 22:45:43 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546454
] 

Jay D. McHugh commented on GERONIMO-3638:
-----------------------------------------

RFC 2396 seems to say the same character set (a portion of latin with numerics and some special
characters).

As far as whether we should be using the Charset.defaultCharset() - You may be right.

Maybe we should be either using US-ASCII or ISO-8859-1 explicitly rather than letting the
JVM pick which one we use.

Anyone else have a comment or suggestion?

> 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.


Mime
View raw message